documenting-apis
Generate API specification from codebase - endpoints, types, schemas.
npx skills add majiayu000/claude-skill-registry --skill documenting-apis --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.
# API仕様生成 ## 検出 | カテゴリ | パターン | | -------------- | ------------------------------------ | | エンドポイント | Express, Fastify, Next.js, Flask 等 | | 関数 | tree-sitter, TypeScript, JSDoc | | 型 | interface, type, Zod, Pydantic | | OpenAPI | openapi.yaml, swagger.yaml | | 認証 | Authミドルウェア、JWT、OAuthパターン | ## フレームワークパターン | フレームワーク | パターン | | -------------- | ---------------------------- | | Express | `app.get()`, `router.post()` | | Next.js | `app/api/**/route.ts` | | Flask | `@app.route()` | | FastAPI | `@app.get()`, `@app.post()` |
- 検出
- フレームワークパターン
What does the documenting-apis skill do?
Generate API specification from codebase - endpoints, types, schemas.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill documenting-apis --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.