Agent skill · Backend & API

documentation-generation

Effective technical documentation strategies, API docs, README patterns, and doc generation workflows

Cosmic Stack3,294★ · 2 repos on radarProfile →
claude-codeMIT
Install
npx skills add cosmicstack-labs/mercury-agent-skills --skill documentation-generation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 17 KB
Bundled scripts: none
Version: 1.0.0
Declared author: cosmicstack-labs
Path: categories/development/documentation-generation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 364
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Documentation Generation Write documentation that people actually read, understand, and trust — with automated workflows that keep it accurate. ## Core Principles ### 1. Documentation Is Code — Treat It That Way Store docs in the repository, version them with code, review them in PRs, lint them in CI. Documentation that lives in a separate wiki inevitably drifts from reality. ### 2. Write for the Reader's Context Different readers need different documents. A junior developer onboarding needs a step-by-step tutorial. A senior engineer debugging needs API reference. A product manager needs architecture overviews. ### 3. Show, Don't Just Tell Code examples are worth a thousand words of prose. Every API, every workflow, every pattern should be accompanied by a complete, runnable example. ### 4. Document Why, Not Just What The code already tells you what it does. Documentation should explain the reasoning, the tradeoffs, and the edge cases that aren't obvious from reading the implementation. --- ## Documentation Maturity Model | Level | Coverage | Accuracy | Tooling | Maintenance | |-------|----------|----------|---------|-------------| | **1: Skeleton** | README only | Often outdated

What's inside
Steps it walks through
  1. Core Principles
  2. 1. Documentation Is Code — Treat It That Way
  3. 2. Write for the Reader's Context
  4. 3. Show, Don't Just Tell
  5. 4. Document Why, Not Just What
  6. Documentation Maturity Model
  7. Actionable Guidance
  8. The README Pattern
  9. API Documentation Patterns
  10. Doc-as-Code Workflows
  11. Documentation Types and When to Use Them
  12. Automated Changelog Generation
  13. Writing Style Guide
  14. README Quality Checklist
Commands it runs
Generate a Python client
openapi-generator generate -i openapi.yaml -g python -o client-python
Generate TypeScript types
openapi-generator generate -i openapi.yaml -g typescript-axios -o client-ts
Generate interactive docs (redoc)
npx redoc-cli bundle openapi.yaml -o docs/api.html
Swagger UI (docker)
docker run -p 80:8080 -e SWAGGER_JSON=/openapi.yaml -v $(pwd):/tmp swaggerapi/swagger-ui
TypeScript Documentation Generator
npx typedoc --out docs/api src/
More from mercury-agent-skills
All skills →
About this skill
What does the documentation-generation skill do?

Effective technical documentation strategies, API docs, README patterns, and doc generation workflows

How do I install it?

Run `npx skills add cosmicstack-labs/mercury-agent-skills --skill documentation-generation --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 cosmicstack-labs/mercury-agent-skills, a repository with 364 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.

Keep going