About openapi-spec-generation
A skill for creating, maintaining, and validating OpenAPI 3.1 specifications for REST APIs. It serves developers working from API design through implementation validation and documentation.
Key features
- 01Create OpenAPI specifications
- 02Generate specs from existing code
- 03Design API contracts
- 04Validate implementations against specs
- 05Generate client SDKs
Use cases
- 01Document a REST API from scratch
- 02Derive a spec from existing code
- 03Check an API implementation against its contract
- 04Generate client SDKs from a spec
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill openapi-spec-generationAfter installing, type/openapi-spec-generationin Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMEOpenAPI Spec Generation
Comprehensive patterns for creating, maintaining, and validating OpenAPI 3.1 specifications for RESTful APIs.
Use this skill when
- Creating API documentation from scratch
- Generating OpenAPI specs from existing code
- Designing API contracts (design-first approach)
- Validating API implementations against specs
- Generating client SDKs from specs
- Setting up API documentation portals
Do not use this skill when
- The task is unrelated to openapi spec generation
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments
Markdown supported