From quality
Analyze OpenAPI and Postman schemas for MCP tool generation. Use when analyzing API specifications, extracting endpoint information, generating tool signatures, or when user mentions OpenAPI, Swagger, API schema, endpoint analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/quality:api-schema-analyzerThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill analyzes OpenAPI/Swagger and Postman collection schemas to extract endpoint information for generating MCP tools.
This skill analyzes OpenAPI/Swagger and Postman collection schemas to extract endpoint information for generating MCP tools.
Load OpenAPI Spec
scripts/analyze-openapi.py <openapi.json|yaml>Generate Tool Signatures
scripts/generate-tool-signatures.py <openapi.json> --lang=python|typescriptParse Collection
scripts/analyze-postman.py <collection.json>Map to MCP Tools
scripts/map-to-mcp-tools.py <collection.json> --output=tools.jsonscripts/analyze-openapi.py - Parse OpenAPI specs (v2, v3)scripts/analyze-postman.py - Parse Postman collectionsscripts/generate-tool-signatures.py - Generate function signaturesscripts/map-to-mcp-tools.py - Map API endpoints to MCP toolsscripts/extract-schemas.sh - Extract request/response schemasExample 1: Analyze OpenAPI Spec
# Extract all endpoints and parameters
./scripts/analyze-openapi.py api-spec.json
# Generate Python tool signatures
./scripts/generate-tool-signatures.py api-spec.json --lang=python
Example 2: Map Postman to MCP
# Analyze Postman collection
./scripts/analyze-postman.py my-api.json
# Generate MCP tool mappings
./scripts/map-to-mcp-tools.py my-api.json --output=mcp-tools.json
pyyaml, jsonschema packagesnpx claudepluginhub vanman2024/dev-lifecycle-marketplace --plugin qualityGenerates or updates OpenAPI 3.0 specs by scanning codebases for API route definitions in Express, Python, Go, Java Spring, and Rails projects. Use to create or update API documentation from existing endpoints.
Generates OpenAPI 3.0+ specs from existing API code, enhances with schemas/examples/errors, creates interactive docs/SDKs, and validates compliance.
Generates and maintains OpenAPI 3.1 specifications from code, design-first specs, and validation patterns for RESTful APIs. Use for API documentation, SDK generation, and contract compliance.