api-documentation
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
Best use case
api-documentation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
Teams using api-documentation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/api-documentation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api-documentation Compares
| Feature / Agent | api-documentation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# API Documentation Workflow ## Overview Specialized workflow for creating comprehensive API documentation including OpenAPI/Swagger specs, developer guides, code examples, and interactive documentation. ## When to Use This Workflow Use this workflow when: - Creating API documentation - Generating OpenAPI specs - Writing developer guides - Adding code examples - Setting up API portals ## Workflow Phases ### Phase 1: API Discovery #### Skills to Invoke - `api-documenter` - API documentation - `api-design-principles` - API design #### Actions 1. Inventory endpoints 2. Document request/response 3. Identify authentication 4. Map error codes 5. Note rate limits #### Copy-Paste Prompts ``` Use @api-documenter to discover and document API endpoints ``` ### Phase 2: OpenAPI Specification #### Skills to Invoke - `openapi-spec-generation` - OpenAPI - `api-documenter` - API specs #### Actions 1. Create OpenAPI schema 2. Define paths 3. Add schemas 4. Configure security 5. Add examples #### Copy-Paste Prompts ``` Use @openapi-spec-generation to create OpenAPI specification ``` ### Phase 3: Developer Guide #### Skills to Invoke - `api-documentation-generator` - Documentation - `documentation-templates` - Templates #### Actions 1. Create getting started 2. Write authentication guide 3. Document common patterns 4. Add troubleshooting 5. Create FAQ #### Copy-Paste Prompts ``` Use @api-documentation-generator to create developer guide ``` ### Phase 4: Code Examples #### Skills to Invoke - `api-documenter` - Code examples - `tutorial-engineer` - Tutorials #### Actions 1. Create example requests 2. Write SDK examples 3. Add curl examples 4. Create tutorials 5. Test examples #### Copy-Paste Prompts ``` Use @api-documenter to generate code examples ``` ### Phase 5: Interactive Docs #### Skills to Invoke - `api-documenter` - Interactive docs #### Actions 1. Set up Swagger UI 2. Configure Redoc 3. Add try-it functionality 4. Test interactivity 5. Deploy docs #### Copy-Paste Prompts ``` Use @api-documenter to set up interactive documentation ``` ### Phase 6: Documentation Site #### Skills to Invoke - `docs-architect` - Documentation architecture - `wiki-page-writer` - Documentation #### Actions 1. Choose platform 2. Design structure 3. Create pages 4. Add navigation 5. Configure search #### Copy-Paste Prompts ``` Use @docs-architect to design API documentation site ``` ### Phase 7: Maintenance #### Skills to Invoke - `api-documenter` - Doc maintenance #### Actions 1. Set up auto-generation 2. Configure validation 3. Add review process 4. Schedule updates 5. Monitor feedback #### Copy-Paste Prompts ``` Use @api-documenter to set up automated doc generation ``` ## Quality Gates - [ ] OpenAPI spec complete - [ ] Developer guide written - [ ] Code examples working - [ ] Interactive docs functional - [ ] Documentation deployed ## Related Workflow Bundles - `documentation` - Documentation - `api-development` - API development - `development` - Development ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
notion-research-documentation
Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
documentation
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
documentation-templates
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
documentation-generation-doc-generate
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
code-documentation-doc-generate
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
code-documentation-code-explain
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels.
api-documentation-generator
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".