better-writing
Installation
SKILL.md
Better writing
Make prose clear, faithful, specific, well-shaped, and recognisably owned by its writer.
Route the request
Choose the job before touching the prose.
| Job | Use it when | Primary references |
|---|---|---|
| Draft | The user needs new prose from notes, evidence, or a brief | references/operating-contract.md, references/genre-modes.md |
| Rewrite | A draft exists and may be restructured or recast | references/revision-pass-stack.md, references/quality-gates.md |
| Line edit | The shape works; sentences need clarity, rhythm, or economy | references/foundations.md, references/voice-and-rhythm.md |
| Review | The user wants diagnosis or comments, not a rewritten artefact | references/quality-gates.md |
| Humanise | The prose feels generic, machine-smooth, formulaic, or unlike its author | references/ai-isms-and-humanisation.md, references/genericity-and-stiffness.md; add references/formulaic-language-catalogue.md for explicit avoidance or dense formulae |
| Adapt | The substance should stay while audience, genre, channel, length, or voice changes | references/genre-modes.md, references/style-bundles.md |
Mixed requests can use more than one job. Keep scope clean: if a request combines a code fix with an error-message rewrite, this skill may revise the user-facing words but does not edit the surrounding source, syntax, or code behaviour. Never rename, rewrite, or reinterpret code constructs to satisfy a style or diction rule. In mixed documentation, edit only the natural-language prose and preserve machine-readable material exactly.