docs
SolidImproves and simplifies this repo's documentation without losing a fact — finds contradictions between surfaces, duplicated facts, sentences no longer true of the binary, pages nobody links, and prose a reader cannot act on; proposes the smaller true version through the second-family door. Use "simplify the docs", "is the README still true", "docs review", "too long", "where should this go".
Install
Quality Score: 87/100
Skill Content
Details
- Author
- assaio
- Repository
- assaio/assaio
- Created
- 2 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
write-docs
Write and edit project docs (README/markdown) as a glossary of principles, not a mirror of the code. Use when creating or revising a README; when a doc enumerates exact scenes, scenarios, helpers, class ids, file lists, or command/flag matrices the code already holds; when trimming narrative or changelog out of a doc; or when deduplicating overlapping docs and wiring a root doc to its sub-docs.
docs
Create or refresh this repo's README.md, CLAUDE.md and mkdocs.yml, detecting project metadata from git and the manifest. Preserves hand-written prose. Writes files only — no commit, no branch, no PR.
docs-structure
Check, build and fill a repository's Markdown documentation from what the repository actually contains. Read-only by default - reports which docs a repo needs (derived from its code, configs and history, not a fixed list), which existing doc covers each concern whatever its file name, and what is unreachable, oversized, dead-linked or cited by line number. On request it lays down skeleton docs for uncovered concerns and drafts them sentence by sentence from repo evidence with the source in brackets, marked for review. Use for docs layout, a docs index, orphaned or oversized docs, splitting a big doc, owner lines, setting up docs for a new repo, or drafting an architecture, deployment, data-model or API doc from the repo. Not for whether existing prose is still true or has missed a code change (use docs-sync-audit) and not for source-code structure (use repo-health-audit).