write-clearly
Draft, edit, proofread, audit, and apply human feedback to intentional prose stored in software repositories while preserving meaning, language, voice, and format. Use for tasks that materially create or change repository prose, including documentation, plans, policies, release notes, wording in comments or docstrings, UI copy, errors, CLI help, localization strings, articles, brand writing, and personal nonfiction; also use for plain-language, clarity, tone, audience-fit, house-style, or voice-matching requests in any language. Do not use for creating or maintaining authoritative repository verification context unless the task is limited to its wording; without an explicit $verification-context invocation, that remains ordinary repository work. Also exclude semantic source-comment health, stale-comment, TODO, commented-out-code, or machine-directive audits; code-only work; translation-only requests; summarization; data extraction; factual verification; and poetry or fiction unless explicitly invoked.
- License
- MIT
Pinned to revision 406e174a7d0c, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/write-clearly/SKILL.md
- skills/write-clearly/agents/openai.yaml
- skills/write-clearly/references/decision-model-and-fidelity.md
- skills/write-clearly/references/document-functions-and-profiles.md
- skills/write-clearly/references/editorial-diagnostics.md
- skills/write-clearly/references/formats-safety-and-review.md
- skills/write-clearly/references/google-developer-documentation.md
- skills/write-clearly/references/language-voice-and-accessibility.md
- skills/write-clearly/references/methods-sources-and-licenses.md
- skills/write-clearly/scripts/check_prose_fidelity.py
Every link opens the file at its source, pinned to the revision this page describes.