This skill helps developers create professional API documentation with OpenAPI specs, interactive Swagger UI, code examples, and reference guides for REST and GraphQL APIs.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "api-documentation". Create OpenAPI spec for user management API
Expected outcome:
A complete OpenAPI 3.0 specification with /users endpoint, pagination, authentication, and response schemas
Using "api-documentation". Document the authentication flow
Expected outcome:
Step-by-step guide: 1. Login endpoint returns JWT, 2. Include Bearer token in Authorization header, 3. Token refresh mechanism, 4. Example curl commands
Using "api-documentation". Define API reference structure
Expected outcome:
Organized docs with: Overview, Authentication, Endpoints grouped by resource, Error Codes, Rate Limiting, Changelog
Security Audit
SafeAll 79 static findings are false positives. The skill contains only documentation templates with example URLs and code blocks. No actual shell commands, network exfiltration, or cryptographic vulnerabilities exist. The scanner triggered on markdown code delimiters, placeholder URLs in examples, and JWT authentication mentions in OpenAPI specs.
Quality Score
What You Can Build
Internal API Development
Document internal microservices APIs for frontend-backend team collaboration
Public API Release
Create professional documentation for external developers consuming your API
SDK Documentation
Generate comprehensive guides and reference docs for library consumers
Try These Prompts
Create an OpenAPI 3.0 specification for a REST API endpoint that manages users. Include GET (list), POST (create), GET by ID, PUT (update), DELETE endpoints. Define request/response schemas with proper HTTP status codes.
Document a protected API endpoint that requires JWT authentication. Include the auth flow, bearer token usage, 401/403 error responses, and example curl commands for authenticated requests.
Create a comprehensive error handling guide for a REST API. Document all common error codes (400, 401, 403, 404, 409, 429, 500), their meanings, example error responses, and recommended client handling approaches.
Set up Swagger UI for an Express.js API. Show how to integrate swagger-ui-express, load an OpenAPI YAML file, configure custom CSS, and mount the docs at /api-docs.
Best Practices
- Provide working code examples in multiple languages (JavaScript, Python, curl)
- Always document both success and error response cases with examples
- Keep documentation synchronized with API changes using changelogs
Avoid
- Using real API keys or passwords in example code
- Leaving vague descriptions like 'returns data' without specifics
- Missing error case documentation for failure scenarios
Frequently Asked Questions
What OpenAPI version does this skill support?
Can I generate documentation for GraphQL APIs?
How do I set up interactive Swagger UI?
What authentication methods are supported?
Can this skill test my actual API endpoints?
How do I document rate limiting?
Developer Details
Author
supercent-ioLicense
MIT
Repository
https://github.com/supercent-io/skills-template/tree/main/.agent-skills/api-documentation/Ref
main
File structure
📄 SKILL.md