amey-thakur/ai-skills/editing-and-revision
Claude Code and agent skill by amey-thakur/ai-skills
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install amey-thakur/ai-skills/editing-and-revisionSKILL.md
The same SKILL.md was published earlier as amey-thakur/ai-skills/editing-and-revision.
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).
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/writing/editing-and-revision/SKILL.md
Popularity
- Repository stars
- 10
- Repository forks
- 2
- 7-day trend score
- 17
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/amey-thakur/ai-skills/editing-and-revision)