Menu

Individual skill

documentation-pro

0upvotes

Write documentation developers actually use: READMEs, API docs, ADRs, runbooks, and docs-as-code workflows. Use when writing or improving technical documentation.

skills/documentation-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Documentation Pro

## Overview

Good documentation — **accurate, findable, and maintained** — is a force multiplier; bad
documentation (missing, wrong, or rotting) is worse than none because it actively misleads. This
skill covers writing docs developers actually use: READMEs that onboard, API docs that answer
questions, ADRs that preserve decisions, runbooks that work at 3am, and the docs-as-code workflows
that keep everything from rotting.

The through-line: docs are a product with users — write for their tasks, keep them next to the code.

## When to use
Back to top