Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
charon-fan avatar

Api Documenter

  • 659 installs
  • 65 repo stars
  • Updated June 21, 2026
  • charon-fan/agent-playbook

api-documenter is a Claude Code skill that generates and validates OpenAPI 3.0 specifications for developers who need REST API documentation before shipping SDKs or public docs.

About

api-documenter is an agent-playbook skill for producing OpenAPI 3.0 and Swagger-compatible API documentation from existing REST services. It follows RESTful conventions with clear resource naming, complete request and response schemas, authentication requirements, and standardized error formats. Bundled Python scripts generate specs via generate_openapi.py and validate them with validate_openapi.py against openapi.yaml. Developers invoke api-documenter when they need machine-readable API contracts for SDK generation, partner integrations, or developer portals.

  • OpenAPI 3.0.3 generation following RESTful resource naming and complete request/response shapes
  • Documents authentication requirements and standardized error response formats
  • Python scripts: generate_openapi.py and validate_openapi.py for spec creation and linting
  • Ships reference OpenAPI YAML examples for health checks and minimal APIs
  • Part of the agent-playbook collection with natural-language triggers like “Document this API”

Api Documenter by the numbers

  • 659 all-time installs (skills.sh)
  • Ranked #338 of 1,901 Documentation skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/charon-fan/agent-playbook --skill api-documenter

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs659
repo stars65
Security audit3 / 3 scanners passed
Last updatedJune 21, 2026
Repositorycharon-fan/agent-playbook

How do you generate OpenAPI 3.0 docs from a REST API?

Generate and validate OpenAPI 3.0 specs so your API is documented before you ship SDKs or public docs.

Who is it for?

Backend developers documenting REST APIs who need generated and validated OpenAPI 3.0 specs with Python helper scripts.

Skip if: GraphQL-only APIs or teams that already maintain hand-written specs with no generation or validation gap.

When should I use this skill?

The user asks to document an API, create an OpenAPI spec, or generate Swagger-compatible REST documentation.

What you get

An OpenAPI 3.0 YAML spec with validated request, response, auth, and error schemas ready for SDK or portal publishing.

  • openapi.yaml
  • validated OpenAPI 3.0 specification

By the numbers

  • Includes 2 Python scripts: generate_openapi.py and validate_openapi.py

Files

SKILL.mdMarkdownGitHub ↗

API Documenter

Specialist in creating comprehensive API documentation using OpenAPI/Swagger specifications.

When This Skill Activates

Activates when you:

  • Ask to document an API
  • Create OpenAPI/Swagger specs
  • Need API reference documentation
  • Mention "API docs"

OpenAPI Specification Structure

openapi: 3.0.3
info:
  title: API Title
  version: 1.0.0
  description: API description
servers:
  - url: https://example.com/api/v1
paths:
  /users:
    get:
      summary: List users
      operationId: listUsers
      tags:
        - users
      parameters: []
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/User'
components:
  schemas:
    User:
      type: object
      properties:
        id:
          type: string
        name:
          type: string

Endpoint Documentation

For each endpoint, document:

Required Fields

  • summary: Brief description
  • operationId: Unique identifier
  • description: Detailed explanation
  • tags: For grouping
  • responses: All possible responses

Recommended Fields

  • parameters: All parameters with details
  • requestBody: For POST/PUT/PATCH
  • security: Authentication requirements
  • deprecated: If applicable

Example

/users/{id}:
  get:
    summary: Get a user by ID
    operationId: getUserById
    description: Retrieves a single user by their unique identifier
    tags:
      - users
    parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
        description: The user ID
    responses:
      '200':
        description: User found
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/User'
      '404':
        description: User not found
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Error'

Schema Documentation

Best Practices

1. Use references for shared schemas 2. Add descriptions to all properties 3. Specify format for strings (email, uuid, date-time) 4. Add examples for complex schemas 5. Mark required fields

Example

components:
  schemas:
    User:
      type: object
      required:
        - id
        - email
      properties:
        id:
          type: string
          format: uuid
          description: Unique user identifier
          example: "550e8400-e29b-41d4-a716-446655440000"
        email:
          type: string
          format: email
          description: User's email address
          example: "user@example.com"
        createdAt:
          type: string
          format: date-time
          description: Account creation timestamp

Authentication Documentation

Document auth requirements:

security:
  - bearerAuth: []

components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Use your JWT token from /auth/login

Error Responses

Standard error format:

components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: Error message
        code:
          type: string
          description: Application-specific error code
        details:
          type: object
          description: Additional error details

Common HTTP status codes:

  • 200: Success
  • 201: Created
  • 204: No Content
  • 400: Bad Request
  • 401: Unauthorized
  • 403: Forbidden
  • 404: Not Found
  • 409: Conflict
  • 422: Unprocessable Entity
  • 500: Internal Server Error

Scripts

Generate OpenAPI spec from code:

python scripts/generate_openapi.py

Validate OpenAPI spec:

python scripts/validate_openapi.py openapi.yaml

References

  • references/openapi-template.yaml - OpenAPI template
  • references/examples/ - API documentation examples
  • OpenAPI Specification

Related skills

FAQ

What OpenAPI version does api-documenter produce?

api-documenter generates OpenAPI 3.0 specifications with RESTful conventions, complete request and response documentation, authentication requirements, and error response formats suitable for SDK and portal publishing.

How does api-documenter validate generated specs?

api-documenter includes python scripts/validate_openapi.py to check openapi.yaml output. Generation runs through python scripts/generate_openapi.py before validation and publication.

Is Api Documenter safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Documentationbackenddocs

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.