from claude-howto27,310
Generates clear, consumable API docs (OpenAPI, endpoint guides, examples) from source code to speed API documentation and SDK examples.
This skill produces structured API documentation from source code patterns and examples. It generates OpenAPI/Swagger specs, per-endpoint documentation, example requests/responses, SDK usage snippets (JavaScript, Python), authentication guides, and error-code references. The output is templated markdown suitable for developer docs or a docs site.
Use this skill when creating or updating API documentation, producing OpenAPI specifications from code, onboarding third-party integrators, or responding to user questions about endpoints, parameters, or response formats. It is useful for automating repetitive doc sections and producing consistent examples.
Likely compatible with Claude Code-style agents and general-purpose code-assistant agents that can run small scripts and edit markdown/doc files.
A minimal API documentation template skill written entirely in Ukrainian. Contains only a single endpoint example (GET /users/:id) with parameter table, response samples, and cURL/JS/Python snippets. No scripts, no automation logic — essentially just a static markdown template. The frontmatter description is in Ukrainian but DB metadata is in English, suggesting a language mismatch. Too thin to be practically useful as a skill; an LLM could generate this template from a simple prompt.
Purely a documentation template with no executable components. No security concerns. Very low code quality — no real instructions, just a single example. Architecture is bare-minimum (frontmatter + one section). Usefulness is limited because this is essentially a prompt template an LLM could produce on demand without a skill. Language mismatch between DB metadata (English) and actual content (Ukrainian) is a quality issue.
