Editing and revision
Skill Amey-Thakur/AI-SKILLS/skills/writing/editing-and-revision
Plug-and-play skills and prompts for every AI coding agent
npx -y skills add Amey-Thakur/AI-SKILLS --skill editing-and-revisionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn a rough draft into finished writing through structured revision passes: cut, clarify, then polish. Use when improving your own or others' writing after the first draft exists.
SKILL.md
2.5 KB, as published. Nobody here has run it
Editing and revision
Writing is rewriting. The first draft's job is to exist; revision is where the quality comes from. The mistake is trying to fix everything at once: edit in passes, each with one focus, biggest problems first.
Method
- Separate writing from editing. Do not edit while drafting; the critical voice kills the generative one. Get the draft down, then come back to it, ideally after a break so you read it closer to how a stranger would.
- First pass: structure and argument. Before touching sentences, ask whether the whole thing works: is the point clear, is the order right, does each section earn its place, is anything missing or redundant? Cut or move whole sections here. Polishing prose you will later delete is wasted work (see structure-and-flow).
- Second pass: cut. Most drafts are 20-30% too long. Delete the redundant, the tangential, the throat-clearing, the said-twice. "Murder your darlings": the clever line that does not serve the point goes. Shorter is almost always better (see concise-writing).
- Third pass: clarify sentence by sentence. Now fix the writing itself: vague words, buried subjects, passive voice, tangled clauses, ambiguous pronouns (see clear-writing). Read aloud to catch what the eye misses.
- Last pass: proofread. Grammar, spelling, punctuation, formatting, consistency. This is last because there is no point proofreading a sentence you might cut. A separate, mechanical pass; tools help but do not replace it.
- Get a reader if the stakes justify it. A fresh pair of eyes finds the confusion you are blind to (you know what you meant). Ask them where they got lost or bored, not whether they "liked it" (see design-critique's specific-question ethic, applied to prose).
Boundaries
- Editing improves what is there; it cannot save a piece with nothing to say or the wrong structure, which is why the structure pass comes first and may send you back to rethinking.
- Over-editing sands off voice and life; know when it is good enough and stop (see voice-and-tone). Diminishing returns are real.
- Editing others' work is a different contract: preserve their voice and intent, fix problems not preferences, and separate must-change from nice-to-change (see giving-feedback).