Agent skill · Backend & API

api-generating

Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.

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

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

Facts
Files in the skill folder: 19
SKILL.md size: 1 KB
Bundled scripts: yes
Allowed tools: -Read-Grep-Glob-Write-Bash(python:*)-Bash(./scripts/*:*)
Path: 04-Skills/projects/05-api-generator/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 | Task | Resource | |------|----------| | Identify framework | See `PATTERNS.md` | | Documentation standards | See `STANDARDS.md` | | Example outputs | See `EXAMPLES.md` | ## Process ### Step 1: Identify API Endpoints Look for route definitions. For framework-specific patterns, see `PATTERNS.md`. ### 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 each endpoint. ### Step 4: Create Overview Generate an index using `templates/index.md`. ## Output Formats ### Markdown (Default) Generate markdown suitable for README or docs site. ### OpenAPI/Swagger If requested, generate OpenAPI 3.0 spec. See `templates/openapi.yaml`. ## Automation To auto-detect routes: ```bash python scripts/detect_routes.py <source_directory> ``` To validate OpenAPI spec: ```bash ./scripts/validate_openapi.sh <spec_file> ```

What's inside
Steps it walks through
  1. Quick Reference
  2. Process
  3. Step 1: Identify API Endpoints
  4. Step 2: Extract Information
  5. Step 3: Generate Documentation
  6. Step 4: Create Overview
  7. Output Formats
  8. Markdown (Default)
  9. OpenAPI/Swagger
  10. Automation
Ships with 18 files
  • .claude/skills/api-generating/EXAMPLES.md
  • .claude/skills/api-generating/PATTERNS.md
  • .claude/skills/api-generating/SKILL.md
  • .claude/skills/api-generating/STANDARDS.md
  • .claude/skills/api-generating/scripts/detect_routes.py
  • .claude/skills/api-generating/scripts/validate_openapi.sh
  • .claude/skills/api-generating/templates/endpoint.md
  • .claude/skills/api-generating/templates/index.md
  • .claude/skills/api-generating/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-generating skill do?

Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.

How do I install it?

Run `npx skills add huangjia2019/claude-code-engineering --skill 05-api-generator --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