api-documentation-generator SKILL.md skillA
api-documentation-generator in sickn33/agentic-awesome-skills is at git:20260729.2d74b64 (Jul 29, 2026), graded A.
mdr add sickn33/agentic-awesome-skills/api-documentation-generator@git:20260729.2d74b64This copy is 1 version behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
api-documentation-generator from tmolavi/mcp-agent-skills-hub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tmolavi/mcp-agent-skills-hub
- Path
skills/api-documentation-generator/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260722.c217a35, committed Jul 22, 2026
- Size
- 11,561 bytes
- Repository stars
- 10
- License
- MIT
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# API Documentation Generator ## Overview Automatically generate clear, comprehensive API documentation from your codebase. This skill helps you create professional documentation that includes endpoint descriptions, request/response examples, authentication details, error handling, and usage guidelines. Perfect for REST APIs, GraphQL APIs, and WebSocket APIs. ## When to Use This Skill - Use when you need to document a new API - Use when updating existing API documentation - Use when your API lacks clear documentation - Use when onboarding new developers to your API - Use when preparing API documentation for external users - Use when creating OpenAPI/Swagger specifications ## How It Works ### Step 1: Analyze the API Structure First, I'll examine your API codebase to understand: - Available endpoints and routes - HTTP methods (GET, POST, PUT, DELETE, etc.) - Request parameters and body structure - Response formats and status codes - Authentication and authorization requirements - Error handling patterns ### Step 2: Generate Endpoint Documentation For each endpoint, I'll create documentation including: **Endpoint Details:** - HTTP method and URL path …
Read the whole file at its exact version.
How to install
mdr add tmolavi/mcp-agent-skills-hub/api-documentation-generator@git:20260722.c217a35Pins git:20260722.c217a35 in mdr.lock, 1 version behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ghxr4w72jamnv3ad/21399689a47e72d39637d53a8d740037f994e36cef540c66033d76ca4f27c011.json
Then /plugin install api-documentation-generator@markdownregistry-ghxr4w72jamnv3ad in Claude Code. It installs git:20260722.c217a35, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add tmolavi/mcp-agent-skills-hub/api-documentation-generator@sha256:21399689a47e72d3The older copy line above pins the label git:20260722.c217a35, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ghxr4w72jamnv3ad)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest sickn33/agentic-awesome-skills/api-documentation-generator, and what changed since 2139968? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of api-documentation-generator from somewhere else? Ask it: where did my api-documentation-generator come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jul 22, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20260729.2d74b64 of api-documentation-generator in sickn33/agentic-awesome-skills (plugins/agentic-awesome-skills-claude/skills/api-documentation-generator/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260708.a07936c, which it committed on Jul 8, 2026, before this repository did; graded A, 1 version behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/api-documentation-generator/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11561 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tmolavi/mcp-agent-skills-hub · 10 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ghxr4w72jamnv3ad GET https://markdownregistry.com/api/v1/resolve?ref=tmolavi/mcp-agent-skills-hub/api-documentation-generator GET https://markdownregistry.com/api/v1/blob/21399689a47e72d39637d53a8d740037f994e36cef540c66033d76ca4f27c011
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from tmolavi/mcp-agent-skills-hub
Every file in tmolavi/mcp-agent-skills-hub