api-reference-documentation · secondsky — Claude Code skill: OpenAPI docs
Turns an OpenAPI spec into a developer-facing API reference: endpoints, auth, request and response examples. Useful for SDK docs and developer portals.
npx skills add secondsky/claude-skills --skill api-reference-documentation -a claude-codeWhat api-reference-documentation does
The skill walks the agent through an OpenAPI 3.0 spec: the info block with contact details, a servers list for production and staging, a bearerAuth security scheme with JWT format, paths with parameters and responses, and components such as Product and ProductList. A YAML skeleton is included, along with a checklist covering every endpoint with examples, authentication, error responses, rate limits, pagination, webhooks, and SDK samples in several languages.
On practice, it advises sticking to OpenAPI 3.0 or newer, adding request and response examples, documenting parameters and headers, keeping versioned docs, and writing migration guides for breaking changes. For interactive browsing it names Swagger Editor and Swagger UI, Redoc, Postman Documentation, and Stoplight. Pick whichever fits your stack; nothing is pinned.
Install runs through npx skills add for Claude, Codex, Cursor, Gemini CLI, and OpenCode, while GitHub Copilot uses gh skill install. The skill file lands in the platform directory, for example ~/.claude/skills/api-reference-documentation/SKILL.md. If your project already has its own endpoint naming scheme, the skeleton spec will not match it, so check the paths before generating.
What it helps with
- document a REST API from an OpenAPI 3.0 spec
- add request and response examples to every endpoint
- explain bearer token authentication
- build a checklist for errors, rate limits and pagination
- write a migration guide for breaking changes
Example prompts for the agent
- Generate an OpenAPI 3.0 spec for a products and orders API with production and staging servers
- Document the /products endpoint with limit and category parameters and a sample response
- Run my API against the documentation checklist and tell me what is missing
How to install api-reference-documentation
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-reference-documentation -a claude-code2Manually: put the files in place
~/.claude/skills/api-reference-documentation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/api-reference-documentation/
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-reference-documentation -a codex2Manually: put the files in place
.agents/skills/api-reference-documentation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-reference-documentation -a cursor2Manually: put the files in place
.cursor/skills/api-reference-documentation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install secondsky/claude-skills api-reference-documentation2Manually: put the files in place
.github/skills/api-reference-documentation/SKILL.md1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-reference-documentation -a gemini-cli2Platform CLI
gemini skills install https://github.com/secondsky/claude-skills --path plugins/api-reference-documentation/skills/api-reference-documentationManually: put the files in place
.devin/skills/api-reference-documentation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-reference-documentation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about api-reference-documentation
How do I install api-reference-documentation in Claude?
Run npx skills add secondsky/claude-skills --skill api-reference-documentation -a claude-code. The skill ends up at ~/.claude/skills/api-reference-documentation/SKILL.md.
What does api-reference-documentation do?
It guides the agent through writing a REST API reference: endpoints, authentication, request and response examples, and data schemas. It builds on an OpenAPI 3.0 spec.
Which tools does the skill work with?
It names Swagger Editor and Swagger UI, Redoc, Postman Documentation, and Stoplight. No single tool is required.
Source text
SKILL.md · MIT
---
name: api-reference-documentation
description: Creates professional API documentation using OpenAPI specifications with endpoints, authentication, and interactive examples. Use when documenting REST APIs, creating SDK references, or building developer portals.
license: MIT
---
# API Reference Documentation
Create comprehensive API documentation for developer integration.
## OpenAPI 3.0 Specification
```yaml
openapi: 3.0.3
info:
title: E-Commerce API
version: 1.0.0
description: API for managing products and orders
contact:
email: [email protected]
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
© secondsky · MIT · secondsky/claude-skills
Similar skills
Everything for Writing and docs →api-reference-documentation by other authors comes first.