writing-revision
Applies a systematic three-pass revision system (Zinsser, King, Pinker, Clark) to existing drafts — Pass 1 cuts clutter, Pass 2 reduces cognitive load, Pass 3 improves rhythm. Use when revising, editing, or polishing drafts, cutting word count, tightening prose, improving readability, or fixing flow, or when user mentions revision, editing, cut clutter, too wordy, improve readability, fix the flow, reduce word count.
What this skill does
# Writing Revision (Three-Pass System) ## Table of Contents - [Core Principles](#core-principles) - [Workflow](#workflow) - [Pass Overview](#pass-overview) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) **Related skills:** Use `writing-structure-planner` for planning structure, `writing-stickiness` for memorable messaging, `writing-pre-publish-checklist` for final publishing checks. ## Core Principles 1. **One focus per pass**: Each pass targets one dimension rather than fixing everything at once 2. **Cut 10-25%**: King's formula - second draft equals first draft minus 10-25% 3. **Every word earns its place**: If a word doesn't contribute, remove it 4. **First reading is correct reading**: Readers shouldn't need to re-read sentences (Pinker) 5. **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](resources/revision-guide.md) for the complete three-pass system with examples and the full transformation demonstration. 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](resources/revision-guide.md#pass-1-cut-clutter-zinsserking) 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](resources/revision-guide.md#pass-2-reduce-cognitive-load-pinker) 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](resources/revision-guide.md#pass-3-improve-rhythm-clark) for detailed examples. Validate using [resources/evaluators/rubric_revision.json](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 **Requirements:** 1. **Preserve meaning**: Keep the author's intended meaning intact while cutting or restructuring 2. **Analyze before improving**: Always create the analysis file first, then make improvements based on findings 3. **Complete coverage**: Analyze the entire draft in each pass, not just the first few paragraphs 4. **Measure reduction**: Track actual word count reduction in Pass 1 (target 10-25%) 5. **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](resources/revision-guide.md)**: Complete three-pass system with before/after examples - **[resources/evaluators/rubric_revision.json](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
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.