api-documentation-generator

Generate developer-facing API documentation with endpoints, parameters, examples, and error handling.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/DucCuong159/Realtime-chatapp --skill api-documentation-generator-duccuong159
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-documentation-generator
Source: https://github.com/DucCuong159/Realtime-chatapp/tree/main/.agent/skills/api-documentation-generator
Command: npx skills add https://github.com/DucCuong159/Realtime-chatapp --skill api-documentation-generator-duccuong159

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? APIs without clear documentation slow down developer onboarding, increase support tickets, and cause integration errors. This Skill analyzes your codebase and produces complete, consistent API documentation covering endpoints, authentication, errors, and working code examples. ## Core Features & Use Cases - Endpoint Documentation: Generates per-endpoint specs including HTTP methods, path/query parameters, request/response schemas, status codes, and authentication requirements. - Multi-Language Code Examples: Produces working examples in cURL, JavaScript/TypeScript, and Python, plus OpenAPI/Swagger specs and Postman collections. - Error & Auth Coverage: Documents all error codes, troubleshooting steps, token flows, rate limits, and pagination patterns. - Use Case: You just finished a REST API for a chat application. Point this Skill at your routes and receive a full documentation set with a quick-start guide, per-endpoint references, and copy-paste-ready client examples. ## Quick Start Generate complete API documentation for the Express routes in my backend folder, including request examples and error responses.

Frequently Asked Questions about api-documentation-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate API documentation from my code?

Point the Skill at your API codebase and it analyzes routes, HTTP methods, parameters, and response schemas to produce structured documentation. Output includes endpoint references, authentication guides, and code examples in cURL, JavaScript, and Python.

What should good REST API documentation include?

Complete REST API docs include endpoint URLs and methods, request parameters with types and validation rules, success and error responses with status codes, authentication requirements, and working code examples. Rate limits and pagination patterns should also be documented.

Can it generate OpenAPI or Swagger specifications?

Yes, the Skill can produce OpenAPI 3.0 YAML specifications and Postman collections alongside Markdown documentation. These artifacts enable interactive documentation and automated API testing workflows.

Does it support GraphQL and WebSocket API documentation?

Yes, the Skill covers REST, GraphQL, and WebSocket APIs. For GraphQL it documents queries, mutations, variables, and typed error responses; for WebSocket APIs it documents events and message formats.

How do I keep API documentation in sync with code changes?

Generate docs from code comments or annotations, add API tests that validate documented behavior, and review documentation with every API change. Treating docs as part of the code review process prevents drift.

What are the limitations of generated API documentation?

Generated documentation requires human review for environment-specific details, business context, and accuracy of examples. It should not replace testing, validation, or expert review before publishing to external developers.