Agent skill
writing-revision
Use when revising, editing, or polishing an existing draft. Invoke when user mentions revision, editing, cutting clutter, tightening prose, improving readability, fixing rhythm, reducing word count, or improving an existing piece of writing.
Install this agent skill to your Project
npx add-skill https://github.com/lyndonkl/claude/tree/main/skills/writing-revision
SKILL.md
Writing Revision (Three-Pass System)
Table of Contents
- Purpose
- When to Use
- Core Principles
- Workflow
- Pass Overview
- Guardrails
- Quick Reference
Purpose
This skill applies a systematic three-pass revision system drawn from Zinsser, King, Pinker, and Clark. Each pass has a single focus: Pass 1 cuts clutter (make it lean), Pass 2 reduces cognitive load (make it readable), Pass 3 improves rhythm (make it flow). Multiple focused passes produce better results than one comprehensive revision.
When to Use
Use this skill when:
- Revising a draft: User has written content that needs improvement
- Tightening prose: User wants to cut word count or eliminate clutter
- Improving readability: Text is hard to follow or requires re-reading
- Enhancing flow: Writing feels choppy, monotonous, or lacks rhythm
- Polishing before publishing: Final quality improvement pass on prose
Trigger phrases: "revise", "edit my draft", "tighten this", "cut clutter", "too wordy", "improve readability", "fix the flow", "polish", "make it better", "reduce word count", "too long"
Do NOT use for:
- Planning structure from scratch (use
writing-structure-planner) - Making messages memorable (use
writing-stickiness) - Final publishing checklist (use
writing-pre-publish-checklist)
Core Principles
- One focus per pass: Don't try to fix everything at once - each pass targets one dimension
- Cut 10-25%: King's formula - second draft equals first draft minus 10-25%
- Every word earns its place: If a word doesn't contribute, remove it
- First reading is correct reading: Readers shouldn't need to re-read sentences (Pinker)
- Rhythm creates engagement: Varied sentence lengths and strong endings keep readers moving
Workflow
Copy this checklist and track your progress:
Three-Pass Revision:
- [ ] Pass 1: Cut clutter (analyze -> improve)
- [ ] Pass 2: Reduce cognitive load (analyze -> improve)
- [ ] Pass 3: Improve rhythm (analyze -> improve)
Before starting: Review resources/revision-guide.md for the complete three-pass system with examples and the full transformation demonstration.
IMPORTANT: For each pass, analyze the ENTIRE draft first and output findings to an analysis file in the current directory, then read that file to make improvements. This ensures complete coverage.
Pass 1: Cut Clutter (Zinsser/King)
Goal: Cut 10-25% of word count. Make every word earn its place.
Step 1.1 - Analysis: Read ENTIRE draft. Create analysis file writer-pass1-clutter-analysis.md identifying ALL instances of: adverbs (-ly words), qualifiers (very, really, quite, somewhat), passive voice, weak verbs (is, are, was, were, has/have/had), throat-clearing phrases, and cliches. Calculate word count and set target for 10-25% reduction.
Step 1.2 - Improvement: Read analysis file. Work through ENTIRE draft making improvements: remove 70% of adverbs, delete qualifiers, convert passive to active voice, replace weak verbs with action verbs, eliminate throat-clearing, remove cliches. Verify word count reduction meets 10-25% target. Ensure every remaining word earns its place.
See resources/revision-guide.md - Pass 1 for detailed examples.
Pass 2: Reduce Cognitive Load (Pinker)
Goal: Make reading effortless. First reading should be correct reading.
Step 2.1 - Analysis: Read ENTIRE draft. Create analysis file writer-pass2-cognitive-load-analysis.md identifying ALL issues: garden-path sentences (temporarily mislead readers), buried topics, subject-verb-object separated by more than 7 words, ambiguous pronouns, broken topic chains, sentences requiring re-reading.
Step 2.2 - Improvement: Read analysis file. Work through ENTIRE draft: fix garden-path sentences, signal topic at start of each sentence, keep subject-verb-object close, clarify pronouns, repair topic chains, break overly complex sentences. Read aloud to verify no stumbles.
See resources/revision-guide.md - Pass 2 for detailed examples.
Pass 3: Improve Rhythm (Clark)
Goal: Create engaging flow through sentence variety and strong endings.
Step 3.1 - Analysis: Read ENTIRE draft. Create analysis file writer-pass3-rhythm-analysis.md analyzing: sentence lengths for each paragraph (list actual lengths), monotonous patterns (5+ similar-length sentences in a row), last word of each sentence (mark weak endings), gold-coin placement (identify gaps), opportunities for ladder of abstraction (concrete -> general -> concrete), sections lacking variety.
Step 3.2 - Improvement: Read analysis file. Work through ENTIRE draft: add short sentences for emphasis after longer ones, replace weak sentence endings with strong words, distribute gold-coin moments throughout (especially middle), apply ladder of abstraction, vary sentence lengths deliberately. Read aloud to verify flow. Confirm good mix of short, medium, and long sentences.
See resources/revision-guide.md - Pass 3 for detailed examples.
Validate using resources/evaluators/rubric_revision.json. Minimum standard: Average score >= 3.5.
Pass Overview
| Pass | Focus | Method | Target |
|---|---|---|---|
| Pass 1 | Clutter | Zinsser/King | Cut 10-25% word count |
| Pass 2 | Cognitive Load | Pinker | No re-reading needed |
| Pass 3 | Rhythm | Clark | Varied lengths, strong endings |
Guardrails
Critical requirements:
- Preserve meaning: Never change the author's intended meaning while cutting or restructuring
- Analyze before improving: Always create the analysis file first, then make improvements based on findings
- Complete coverage: Analyze the ENTIRE draft in each pass, not just the first few paragraphs
- Measure reduction: Track actual word count reduction in Pass 1 (target 10-25%)
- Read aloud: After Passes 2 and 3, verify by reading aloud for stumbles and rhythm
Common pitfalls:
- Trying to fix everything in one pass (stick to one focus per pass)
- Only revising the opening paragraphs and losing steam
- Cutting so aggressively that voice is lost
- Not tracking actual word count reduction
- Skipping the analysis phase and jumping straight to editing
Quick Reference
Key resources:
- resources/revision-guide.md: Complete three-pass system with before/after examples
- resources/evaluators/rubric_revision.json: Quality scoring criteria
Inputs required:
- Draft text to revise (any stage)
- User's intent or core message (if known)
- Any constraints (word count target, tone preferences)
Outputs produced:
- Analysis files for each pass (clutter, cognitive load, rhythm)
- Revised draft with tracked word count reduction
- Summary of changes made in each pass
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
synthesis-and-analogy
Use when synthesizing information from multiple sources (literature review, stakeholder feedback, research findings, data from different systems), creating or evaluating analogies for explanation or problem-solving (cross-domain transfer, "X is like Y", structural mapping), combining conflicting viewpoints into unified framework, identifying patterns across disparate sources, finding creative solutions by transferring principles from one domain to another, testing whether analogies hold (surface vs deep similarities), or when user mentions "synthesize", "combine sources", "analogy", "like", "similar to", "transfer from", "integrate findings", "what's it analogous to".
socratic-teaching-scaffolds
Use when teaching complex concepts (technical, scientific, philosophical), helping learners discover insights through guided questioning rather than direct explanation, correcting misconceptions by revealing contradictions, onboarding new team members through scaffolded learning, mentoring through problem-solving question frameworks, designing self-paced learning materials, or when user mentions "teach me", "help me understand", "explain like I'm", "learning path", "guided discovery", or "Socratic method".
environmental-scanning-foresight
Use when scanning external trends for strategic planning, monitoring PESTLE forces (Political, Economic, Social, Technological, Legal, Environmental), detecting weak signals (early indicators of change), planning scenarios for multiple futures, setting signposts and indicators for early warning, or when user mentions environmental scanning, horizon scanning, trend analysis, scenario planning, strategic foresight, futures thinking, or emerging issues monitoring.
embedding-fusion-strategy
Use when designing embedding strategies that fuse semantic and structural information for knowledge graphs. Invoke when user mentions node embeddings, structural embeddings, semantic embeddings, contrastive alignment, embedding fusion, vector representations for graphs, or combining text and graph signals. Provides embedding selection, fusion design, and implementation guidance.
constraint-based-creativity
Use when brainstorming feels stuck or generates obvious ideas, need to break creative patterns, working with limited resources (budget/time/tools/materials), want unconventional solutions, designing with specific limitations, user mentions "think outside the box", "we're stuck", "same old ideas", "tight constraints", "limited budget/time", or seeking innovation through limitation rather than abundance.
symmetry-group-identifier
Use when you've identified candidate symmetries and need to map them to mathematical groups for architecture design. Invoke when user mentions cyclic groups, dihedral groups, Lie groups, SO(3), SE(3), permutation groups, or needs to formalize symmetries into group theory language. Provides taxonomy and mathematical foundations from Visual Group Theory principles.
Didn't find tool you were looking for?