mcpbeat

API Generating

huangjia2019/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.

4k tokens
context cost
the whole folder, loaded on every use
9
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
1038
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/huangjia2019/claude-code-engineering --skill api-generating

The instruction itself

11 sections, as written by the author

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:

python scripts/detect_routes.py <source_directory>

To validate OpenAPI spec:

./scripts/validate_openapi.sh <spec_file>

How to use it

Copy the folder

Take huangjia2019/api-generating from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.