Openapi Spec Generation

by wshobson46891e7e60daNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

Instructions onlySoftware Development
AI-generated overview

Guides creation, maintenance and validation of OpenAPI 3.1 specifications for REST APIs.

What it does
This skill provides patterns and guidance for writing, maintaining and validating OpenAPI 3.1 specifications for RESTful APIs. It covers spec structure, design-first, code-first and hybrid approaches, and best practices for reuse, examples, error documentation and versioning. It also points to a reference file containing templates and worked examples.
When to use it
Use it when creating API documentation, generating specs from existing code, designing API contracts before implementation, validating implementations against specs, or generating client SDKs. It also suits setting up API documentation portals.
Requirements
No scripts; instructions only. It relies on a reference file in the skill folder for templates and examples.

OpenAPI Spec Generation

Comprehensive patterns for creating, maintaining, and validating OpenAPI 3.1 specifications for RESTful APIs.

When to Use This Skill

  • 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

Core Concepts

1. OpenAPI 3.1 Structure

yaml
openapi: 3.1.0info:  title: API Title  version: 1.0.0servers:  - url: https://api.example.com/v1paths:  /resources:    get: ...components:  schemas: ...  securitySchemes: ...

2. Design Approaches

ApproachDescriptionBest For
Design-FirstWrite spec before codeNew APIs, contracts
Code-FirstGenerate spec from codeExisting APIs
HybridAnnotate code, generate specEvolving APIs

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

  • Use $ref - Reuse schemas, parameters, responses
  • Add examples - Real-world values help consumers
  • Document errors - All possible error codes
  • Version your API - In URL or header
  • Use semantic versioning - For spec changes

Don'ts

  • Don't use generic descriptions - Be specific
  • Don't skip security - Define all schemes
  • Don't forget nullable - Be explicit about null
  • Don't mix styles - Consistent naming throughout
  • Don't hardcode URLs - Use server variables

Source and attribution

Source:wshobson/agentsinplugins/documentation-generation/skills/openapi-spec-generationat commit46891e7

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Openapi Spec Generation Agent Skill | SourceWeft