api-docs
Generate API documentation from source code with JSDoc and OpenAPI support
npx skills add majiayu000/claude-skill-registry --skill api-docs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Generate API documentation from TypeScript/JavaScript source: 1. **Scan exports**: Find all public functions, classes, and interfaces 2. **Extract JSDoc**: Parse `@param`, `@returns`, `@throws`, `@example` annotations 3. **Generate missing docs**: Add JSDoc for undocumented public APIs 4. **OpenAPI spec**: For HTTP endpoints, generate OpenAPI 3.0 definitions Dispatch via MCP: `mcp__claude-flow__hooks_worker-dispatch({ trigger: "document", scope: "api" })` Conventions: - Every public export must have a JSDoc comment - Include `@param` with type and description - Include `@returns` with type and description - Include `@throws` for known error conditions - Include `@example` for non-obvious usage
What does the api-docs skill do?
Generate API documentation from source code with JSDoc and OpenAPI support
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-docs --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 majiayu000/claude-skill-registry, a repository with 534 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.