Agent skill · Backend & API

api-documenting

Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.

huangjia2019github.com/huangjia2019GitHub ↗
claude-codecan modify filesships scripts
Install
npx skills add huangjia2019/claude-code-engineering --skill 02-progressive-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 19
SKILL.md size: 2 KB
Bundled scripts: yes
Allowed tools: -Read-Grep-Glob-Write
Path: 04-Skills/projects/02-progressive-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,040
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# API Documentation Generator Generate comprehensive API documentation from source code. ## Quick Reference For common documentation patterns, see `PATTERNS.md`. ## Documentation Standards See `STANDARDS.md` for our documentation conventions. ## Process ### Step 1: Identify API Endpoints Look for: - Route definitions (Express, FastAPI, etc.) - Controller methods - Handler functions ### Step 2: Extract Information For each endpoint, extract: - HTTP method (GET, POST, PUT, DELETE, etc.) - Path/route - Parameters (path, query, body) - Request/response schemas - Authentication requirements ### Step 3: Generate Documentation Use the template in `templates/endpoint.md` for consistent formatting. ### Step 4: Create Overview Generate an index of all endpoints with the template in `templates/index.md`. ## Output Formats ### Markdown (Default) Generate markdown documentation suitable for README or docs site. ### OpenAPI/Swagger If requested, generate OpenAPI 3.0 spec. See `templates/openapi.yaml` for structure. ## Examples See `EXAMPLES.md` for sample inputs and outputs. ## Scripts To auto-detect routes in common frameworks: ```bash python scripts/detect_routes.py <source_directory> ``` To v

What's inside
Steps it walks through
  1. Quick Reference
  2. Documentation Standards
  3. Process
  4. Step 1: Identify API Endpoints
  5. Step 2: Extract Information
  6. Step 3: Generate Documentation
  7. Step 4: Create Overview
  8. Output Formats
  9. Markdown (Default)
  10. OpenAPI/Swagger
  11. Examples
  12. Scripts
Ships with 18 files
  • .claude/skills/api-documenting/EXAMPLES.md
  • .claude/skills/api-documenting/PATTERNS.md
  • .claude/skills/api-documenting/SKILL.md
  • .claude/skills/api-documenting/STANDARDS.md
  • .claude/skills/api-documenting/scripts/detect_routes.py
  • .claude/skills/api-documenting/scripts/validate_openapi.sh
  • .claude/skills/api-documenting/templates/endpoint.md
  • .claude/skills/api-documenting/templates/index.md
  • .claude/skills/api-documenting/templates/openapi.yaml
  • EXAMPLES.md
  • PATTERNS.md
  • README.md
  • STANDARDS.md
  • scripts/detect_routes.py
  • scripts/validate_openapi.sh
  • templates/endpoint.md
  • templates/index.md
  • templates/openapi.yaml
Commands it runs
python scripts/detect_routes.py <source_directory>
More from claude-code-engineering
All skills →
About this skill
What does the api-documenting skill do?

Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.

How do I install it?

Run `npx skills add huangjia2019/claude-code-engineering --skill 02-progressive-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From huangjia2019/claude-code-engineering, a repository with 1,040 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going