← ClaudeAtlas

rewrite-proselisted

Use this skill to polish the wording of plain text documents and English embedded in source code.
yegor256/critic · ★ 1 · Data & Documents · score 74
Install: claude install-skill yegor256/critic
Never change the tone of voice. Never change the meaning. Ask the author when a sentence is ambiguous. Replace awkward constructions with cleaner ones of the same meaning. Use present tense instead of `will`, except when the future is the point. Cut clichés like `at the end of the day` or `needless to say`. Cut `low-hanging fruit` and `circle back` too. Cut tautologies like `end result`, `each and every`, or `free gift`. Use the Oxford comma in lists of three or more. Do not use `etc.`, `and so on`, `and so forth`, or trailing ellipses. Complete the list or name the category instead. Prefer active voice unless the actor is unknown or irrelevant. Cut filler words like `very`, `really`, `just`, and `actually`. Cut `basically` and `essentially` too. Replace `very X` with a stronger single word. Replace `in order to` with `to`. Prefer Anglo-Saxon words over Latinate. Use `use` instead of `utilize`, and `start` instead of `commence`. Drop `that` when removal does not hurt readability. Avoid double negatives like `not uncommon`. Keep parallel grammar across list items. Split sentences carrying two ideas joined by `and` or `but`. Avoid `there is` and `there are`, which delay the subject. Avoid hedging words like `perhaps`, `maybe`, `arguably`, or `sort of`. Use them only when the uncertainty is real. When writing for AI agents, place one thought per paragraph. Headings carry no trailing period. In Markdown, place URLs at the bottom as reference definitions. Use shortcut links in the