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

Api Reference Documentation

  • 352 installs
  • 202 repo stars
  • Updated August 4, 2026
  • secondsky/claude-skills

api-reference-documentation is a Claude Code skill that creates professional REST API documentation with OpenAPI specifications, authentication, and interactive examples for developers publishing integration guides.

About

api-reference-documentation is an MIT-licensed skill from secondsky/claude-skills (part of a 170-skill collection) that authors API reference material using OpenAPI 3.0.3 with servers, security schemes, path operations, schemas, and JSON examples. It includes a 7-item documentation checklist covering endpoints, auth, errors, rate limits, pagination, webhooks, and multi-language SDK samples, plus guidance for Swagger Editor, Redoc, Postman Documentation, and Stoplight. Use api-reference-documentation when documenting REST endpoints, generating openapi.yaml, or standing up a developer portal consumers can explore interactively.

  • api-reference-documentation

Api Reference Documentation by the numbers

  • 352 all-time installs (skills.sh)
  • +12 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #1,155 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/secondsky/claude-skills --skill api-reference-documentation

Add your badge

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

Listed on Skillselion
Installs352
repo stars202
Last updatedAugust 4, 2026
Repositorysecondsky/claude-skills

How do you write OpenAPI API reference documentation?

Use api-reference-documentation for development tasks

Who is it for?

API developers shipping REST services who need OpenAPI specs and portal-ready reference pages with auth and error coverage.

Skip if: Teams documenting internal runbooks or non-HTTP systems—this skill targets REST API reference and developer portal content.

When should I use this skill?

User asks to document REST APIs, create OpenAPI specs, SDK references, or developer portal pages

What you get

OpenAPI 3.0 specification, endpoint reference pages, auth examples, and interactive documentation setup

  • openapi.yaml specification
  • API reference content
  • Auth and error documentation

By the numbers

  • Uses OpenAPI 3.0.3 specification format
  • Includes a 7-item API documentation checklist
  • Recommends 4 documentation tools: Swagger, Redoc, Postman, and Stoplight

Files

SKILL.mdMarkdownGitHub ↗

API Reference Documentation

Create comprehensive API documentation for developer integration.

OpenAPI 3.0 Specification

openapi: 3.0.3
info:
  title: E-Commerce API
  version: 1.0.0
  description: API for managing products and orders
  contact:
    email: api@example.com

servers:
  - url: https://api.example.com/v1
    description: Production
  - url: https://staging-api.example.com/v1
    description: Staging

security:
  - bearerAuth: []

paths:
  /products:
    get:
      summary: List products
      tags: [Products]
      parameters:
        - name: limit
          in: query
          schema: { type: integer, default: 20 }
        - name: category
          in: query
          schema: { type: string }
      responses:
        '200':
          description: Product list
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProductList'

components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

  schemas:
    Product:
      type: object
      required: [id, name, price]
      properties:
        id: { type: string, format: uuid }
        name: { type: string, maxLength: 200 }
        price: { type: number, minimum: 0 }
        description: { type: string }

Documentation Checklist

  • [ ] All endpoints documented with examples
  • [ ] Authentication methods explained
  • [ ] Error responses specified
  • [ ] Rate limits documented
  • [ ] Pagination explained
  • [ ] Webhooks documented (if applicable)
  • [ ] SDK examples in multiple languages

Best Practices

  • Use OpenAPI 3.0+ specification
  • Include request/response examples
  • Document all parameters and headers
  • Provide authentication examples
  • Enable interactive API exploration
  • Maintain version documentation
  • Include migration guides for breaking changes

Tools

  • Swagger Editor / Swagger UI
  • Redoc
  • Postman Documentation
  • Stoplight

Related skills

How it compares

Pick api-reference-documentation for consumer-facing REST reference and OpenAPI output; use technical-specification skills when the deliverable is an internal engineering spec, not a public API catalog.

FAQ

What OpenAPI version does api-reference-documentation use?

api-reference-documentation standardizes on OpenAPI 3.0.3 with info, servers, securitySchemes, paths, components, and JSON request/response examples. The skill also lists checklist items for errors, rate limits, pagination, and webhooks.

Which publishing tools does api-reference-documentation recommend?

api-reference-documentation points to Swagger Editor and Swagger UI, Redoc, Postman Documentation, and Stoplight for interactive API exploration. It emphasizes versioned docs and migration guides for breaking changes.

Backend & APIsbackendintegrations

This week in AI coding

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

unsubscribe anytime.