openapi-parser

Parse OpenAPI 3.x and Swagger 2.0 specs into structured endpoint catalogs.

4|Updated Jan 13, 2026

Search Tags:#openapi #sdk #codegen #swagger #endpoint #parser #api-docs

Ready to run

npx skills add https://github.com/jhlee0409/claude-plugins --skill openapi-parser

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openapi-parser
Source: https://github.com/jhlee0409/claude-plugins/tree/main/plugins/oas/skills/openapi-parser
Command: npx skills add https://github.com/jhlee0409/claude-plugins --skill openapi-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? OpenAPI 3.x or Swagger 2.0 specifications are often large and complex; this skill parses them to extract a clear, structured catalog of endpoints, schemas, and metadata for downstream tooling such as code generation and documentation.

## Core Features & Use Cases

Endpoint extraction: enumerate paths and operations with operationId, tags, summaries, parameters, and responses.
Schema resolution: resolve $ref references and map schemas to usable types for codegen.
Validation and conversion: detect invalid specs, optionally convert Swagger 2.0 to OpenAPI 3.0 format for consistent processing.
Use Case: Given an API spec, generate a ready-to-consume endpoint catalog to drive SDK generation and API docs.

### Quick Start

Provide a local OpenAPI file path (e.g., openapi.yaml) or a remote URL (e.g., https://api.example.com/openapi.yaml) to start parsing and extraction.

Frequently Asked Questions about openapi-parser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract endpoints from an OpenAPI spec for SDK generation?▼

You can extract endpoints from an OpenAPI spec by parsing the file to enumerate paths and operations, resolving $ref references, and outputting a normalized metadata schema for SDK scaffolding. Provide a local file path or remote URL to start parsing.

Can I parse Swagger 2.0 specs or do I need OpenAPI 3.0 format?▼

You can parse Swagger 2.0 specs directly. The parser validates the structure and optionally converts Swagger 2.0 to OpenAPI 3.0 format to ensure consistent processing and schema resolution across different specification versions.

How do I resolve $ref references in a complex OpenAPI specification?▼

Schema resolution resolves $ref references within the OpenAPI specification and maps schemas to usable types for codegen. This process validates the overall structure while extracting a clear catalog of endpoints and metadata.

What is the best way to generate API documentation from an OpenAPI file?▼

The best way to generate API documentation is to parse the OpenAPI file to extract structured endpoint information. This produces a normalized metadata schema containing paths, operations, parameters, and responses ready for documentation tooling.

Does the OpenAPI parser validate spec structure and detect invalid specifications?▼

Yes, the parser validates the OpenAPI spec structure and detects invalid specifications during the extraction process. It ensures structural integrity before resolving references and generating the normalized endpoint catalog.