Documentation
Writes and updates docs, READMEs, runbooks, specs, and ADRs. Use when documenting a feature, writing a runbook, updating README/setup docs, or recording decisions. Do not use for competitive research briefs or for code comments that only restate the next line.From its SKILL.md
npx -y skills add IcodeNet/agent-skills --skill documentationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 263 tokens by cl100k_base, as published. Nobody here has run it
Documentation
Document the why, the run path, and the contract — not the obvious what.
Workflow
- Audience + job — operator, developer, or agent; one job per section.
- Find the owner doc — update the canonical page; do not create a third copy of the same truth.
- Write — quick start that works; real commands from the project's scripts; link out instead of duplicating.
- Runbooks — steps + verification + rollback.
- ADRs — context, decision, alternatives, consequences (
../architecture/references/adr-template.md). - Verify — commands and paths match current repo reality.
Constraints
- Prefer links to canonical docs over pasting large tables into multiple places.
- Comments in code: why/gotchas only — never restate the next line.
- Delete commented-out code; git keeps history.
Verification
- Correct canonical file updated (or new file justified)
- Quick start / commands match current project scripts and paths
- Runbooks include verify + rollback
- ADRs have alternatives + consequences
- No duplicated “source of truth” that already lives elsewhere
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.