Stats
Actions
Tags
From critic
Use this skill when the user wants to polish the wording of plain text documents and English embedded in source code, cutting filler and AI tells.
How this skill is triggered — by the user, by Claude, or both
Slash command
/critic:rewrite-proseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Never change tone of voice.
Never change tone of voice. Never change meaning. Ask author when sentence is ambiguous. Replace awkward constructions with cleaner ones of same meaning.
Use present tense instead of will, except when future is 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.
Cut throat-clearing openers like it is worth noting or here is the thing.
Cut manufactured not just X, but Y contrast and state point directly.
Replace vague declarative like the reasons are structural with specifics.
Drop empty absolutes like always or never unless they hold literally.
Rewrite any sentence engineered to read like pull-quote.
Use Oxford comma in lists of three or more.
Do not use etc., and so on, and so forth, or trailing ellipses.
Complete list or name category instead.
Never join two clauses with em dash. Use period or recast sentence instead.
Prefer active voice unless actor is unknown or irrelevant.
Give every verb subject that can perform it.
Cut false agency where abstraction acts like person.
Name real actor in phrases like the decision emerges.
Cut filler words like very, really, just, and actually.
Cut basically and essentially too.
Replace very X with 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.
Resist reflexive three-item rhythm when two items say enough.
Vary sentence length so rhythm never turns metronomic.
Split sentences carrying two ideas joined by and or but.
Avoid there is and there are, which delay subject.
Avoid hedging words like perhaps, maybe, arguably, or sort of.
Use them only when uncertainty is real.
When writing for AI agents, place one thought per paragraph. Headings carry no trailing period. In Markdown, place URLs at bottom as reference definitions. Use shortcut links in body text.
Spell numbers one through nine as words. Spell 10 and up as digits. Keep digits in tables, code, versions, and measurements.
Do not touch author's vocabulary or stylistic choices. Do not touch quoted text, code, or proper names. Do not touch domain jargon used correctly. Make smallest change that fixes problem.
Show original next to non-trivial rewrite. Ask author to confirm meaning survives. Read result once and remove anything that still sounds machine-generated.
Reflow every touched sentence when file uses one-sentence-per-line layout. Leave existing line breaks alone otherwise.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub yegor256/plugins --plugin critic