Openapi spec generator

Skill a5c-ai/babysitter/library/specializations/sdk-platform-development/skills/openapi-spec-generator

Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration

Install

npx -y skills add a5c-ai/babysitter --skill openapi-spec-generator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Automated OpenAPI specification generation from code annotations, comments, and interface definitions

SKILL.md

2.4 KB, as published. Nobody here has run it

OpenAPI Spec Generator Skill

Overview

This skill automates the generation of OpenAPI 3.x specifications from code annotations, comments, and interface definitions. It parses source code to extract API endpoints, schemas, and documentation to produce comprehensive and accurate API specifications.

Capabilities

Parse code to extract API endpoints and schemas from annotations
Generate OpenAPI 3.x specifications in YAML or JSON format
Validate spec completeness and correctness against OpenAPI standards
Auto-update specs from code changes with incremental generation
Support multiple frameworks (Express, FastAPI, Spring, ASP.NET, etc.)
Extract request/response schemas from TypeScript types, Python type hints, Go structs
Generate examples from code-level documentation

Target Processes

API Design Specification
API Documentation System
SDK Code Generation Pipeline

Integration Points

Code analysis tools (AST parsers)
Schema validators (Spectral, openapi-spec-validator)
Swagger/OpenAPI tooling ecosystem
IDE extensions for spec preview

Input Requirements

Source code with API route definitions
Annotation/decorator conventions used in the codebase
Target OpenAPI version (3.0.x or 3.1.x)
Output format preference (YAML/JSON)

Output Artifacts

OpenAPI specification file (openapi.yaml or openapi.json)
Validation report with any issues found
Schema extraction summary
Change diff from previous spec version (if applicable)

Usage Example

skill:
  name: openapi-spec-generator
  context:
    sourceDirectory: ./src/api
    framework: express
    outputFormat: yaml
    openapiVersion: "3.1.0"
    includeExamples: true

Best Practices

Use consistent annotation patterns across the codebase
Include JSDoc/docstrings for all endpoints
Define reusable schema components
Validate generated specs before publishing
Version control generated specifications