openapi-spec-generator
Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML/JSON API schema, endpoint documentation, API...
Profile →npx skills add sickn33/agentic-awesome-skills --skill openapi-spec-generator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OpenAPI / Swagger Specification Generator ## When to Use Use this skill when you need generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML/JSON API schema, endpoint documentation, API... Generate complete, valid OpenAPI 3.x or Swagger 2.0 specifications from descriptions, code, or partial specs. ## Workflow ### Step 1 — Gather Context Before writing any YAML/JSON, ask (or infer from context) the following: | Question | Why it matters | |---|---| | OpenAPI 3.x or Swagger 2.0? | Different `info`, `servers`/`host`, `components`/`definitions` structure | | Output format: YAML or JSON? | YAML default unless user specifies JSON | | What does this API do? | Sets `info.title`, `info.description`, tags | | List of endpoints (or code to extract from)? | Core paths object | | Authentication type(s)? | `securitySchemes` — see reference | | Common data models or entities? | `components/schemas` / `definitions` | | Any existing partial spec to extend? | Merge rather than overwrite | If the user provides code (Ex
- When to Use
- Workflow
- Step 1 — Gather Context
- Step 2 — Build the Spec
- Step 3 — Schemas and Models
- Step 4 — Security Schemes
- Step 5 — Parameters
- Step 6 — Response Codes
- Step 7 — Quality Checklist
- Step 8 — Output
- Extracting from Code
- Reference Files
- After Completing the OpenAPI/Swagger Specification design
- Limitations
What does the openapi-spec-generator skill do?
Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML/JSON API schema, endpoint documentation, API...
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill openapi-spec-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.