About documentation
A skill for creating maintainable technical documentation across common document types, for teams documenting software and operations. It emphasizes audience needs, useful structure, examples, currency, and links.
Key features
- 01README structure guidance
- 02API reference guidance
- 03Runbook procedures
- 04Architecture and onboarding docs
- 05Audience-focused writing principles
Use cases
- 01Drafting a project README
- 02Documenting API endpoints and errors
- 03Writing operational runbooks
- 04Preparing architecture or onboarding guides
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/documentationin Claude Code to confirm it loaded.
Details
From the project READMETechnical Documentation
Write clear, maintainable technical documentation for different audiences and purposes.
Document Types
README
- What this is and why it exists
- Quick start (< 5 minutes to first success)
- Configuration and usage
- Contributing guide
API Documentation
- Endpoint reference with request/response examples
- Authentication and error codes
- Rate limits and pagination
- SDK examples
Runbook
- When to use this runbook
- Prerequisites and access needed
- Step-by-step procedure
- Rollback steps
- Escalation path
Architecture Doc
- Context and goals
- High-level design with diagrams
- Key decisions and trade-offs
- Data flow and integration points
Onboarding Guide
- Environment setup
- Key systems and how they connect
- Common tasks with walkthroughs
- Who to ask for what
Principles
- Write for the reader — Who is reading this and what do they need?
- Start with the most useful information — Don't bury the lede
- Show, don't tell — Code examples, commands, screenshots
- Keep it current — Outdated docs are worse than no docs
- Link, don't duplicate — Reference other docs instead of copying
Comments
Markdown supported