plugins/rhetorician/skills/copy-editor/SKILL.md
Performs line-level prose editing — pruning adverbs, activating voice, cutting redundancy, and enforcing parallel structure for concision and readability. Use when revising any written content, even if the request is just 'make this better,' 'tighten this up,' or 'clean up the writing.'
npx skillsauth add joellewis/skill-library copy-editorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Copy-editing is the tactical refinement of prose at the sentence level. It transforms a "Shitty First Draft" into vigorous, clear communication by pruning adverbs, activating the voice, and expunging fad words. The goal is to ensure that every word "tells" and that the reader never stumbles over convoluted logic or unnecessary complexity.
Treat editing as a process of checking every tooth. Once the "Down Draft" (getting thoughts on paper) is complete, perform a meticulous "Dental Draft" to see if each sentence is loose, cramped, or healthy.
Vigorous writing is concise. If a word does not add meaning, cut it. Eliminate qualifiers (e.g., "very," "rather," "basically") and "verbal false limbs" (e.g., "the fact that," "in order to").
The active voice is more direct and forceful. Replace passive constructions ("The report was written by him") with active ones ("He wrote the report"). This usually results in shorter, stronger sentences.
Mercilessly go after "fad words" that have lost their meaning through overusage (e.g., "pivot," "proactive," "iconic," "reach out"). Replace them with specific, accurate English.
Adverbs are often a sign of weak verbs. Instead of "he ran quickly," use "he sprinted." Use blue highlights (figuratively or literally) to identify adverbs and replace them with stronger verbs or nouns.
Acknowledge that your first draft is supposed to be bad. Do not edit while writing. Get everything on the page through your "one-inch picture frame."
Review the draft specifically for:
Identify and fix readability "Red Flags":
Scan for repetition. If a unique or "expensive" word (e.g., "horripilation") is used once, it adds flavor; if used twice, it becomes a mannerism. Check for overused transitions like "but" or "however."
Read the entire piece aloud. Your ear will catch the "mechanical symmetry" and clunky rhythms that your eye misses. If you run out of breath before finishing a sentence, it is too long.
REQUIRED SUB-SKILL: None. RECOMMENDED SUB-SKILL: non-fiction-precision — to ensure the structure is sound before fixing the sentences.
databases
Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignment, and conflict-resolution protocol.
development
Use when you need to map who has power, who will be affected, and what motivates each party — produces a stakeholder map as an analytical artifact. This skill identifies and categorizes stakeholders; it does not persuade or influence them (use influence-architect for that).
testing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
testing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.