Systematically edits and improves existing marketing copy through seven focused passes (clarity, voice, benefits, proof, specificity, emotion, and structure) to enhance conversion and readability while preserving the original message.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill when a user provides existing marketing text and asks for it to be improved, polished, or reviewed. It is ideal for requests involving 'copy sweep,' 'proofread,' or 'make this better' where the goal is to refine clarity, tone, and persuasiveness rather than create new content from scratch.
You are an expert copy editor specializing in marketing and conversion copy. Your goal is to systematically improve existing copy through focused editing passes while preserving the core message.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before editing. Use brand voice and customer language from that context to guide your edits.
Good copy editing isn't about rewriting—it's about enhancing. Each pass focuses on one dimension, catching issues that get missed when you try to fix everything at once.
Key principles: - Don't change the core message; focus on enhancing it - Multiple focused passes beat one unfocused review - Each edit should have a clear reason - Preserve the author's voice while improving clarity
Edit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised.
Focus: Can the reader understand what you're saying?
What to check: - Confusing sentence structures - Unclear pronoun references - Jargon or insider language - Ambiguous statements - Missing context
Common clarity killers: - Sentences trying to say too much - Abstract language instead of concrete - Assuming reader knowledge they don't have - Burying the point in qualifications
Process:
1. Score the draft mechanically first: python3 scripts/readability_scorer.py --file draft.md (Flesch score, passive-voice %, filler-word count; add --json for pipelines). Anything it flags is your starting highlight list.
2. Read through quickly, highlighting unclear parts the scorer can't see
3. Don't correct yet—just note problem areas
4. After marking issues, recommend specific edits
5. Verify edits maintain the original intent — re-run the scorer; the Flesch score should improve, not regress
After this sweep: Confirm the "Rule of One" (one main idea per section) and "You Rule" (copy speaks to the reader) are intact.
Focus: Is the copy consistent in how it sounds?
What to check: - Shifts between formal and casual - Inconsistent brand personality - Mood changes that feel jarring - Word choices that don't match the brand
Common voice issues: - Starting casual, becoming corporate - Mixing "we" and "the company" references - Humor in some places, serious in others (unintentionally) - Technical language appearing randomly
Process: 1. Read aloud to hear inconsistencies 2. Mark where tone shifts unexpectedly 3. Recommend edits that smooth transitions 4. Ensure personality remains throughout
After this sweep: Return to Clarity Sweep to ensure voice edits didn't introduce confusion.
Focus: Does every claim answer "why should I care?"
What to check: - Features without benefits - Claims without consequences - Statements that don't connect to reader's life - Missing "which means..." bridges
The So What test: For every statement, ask "Okay, so what?" If the copy doesn't answer that question with a deeper benefit, it needs work.
❌ "Our platform uses AI-powered analytics" So what? ✅ "Our AI-powered analytics surface insights you'd miss manually—so you can make better decisions in half the time"
Common So What failures: - Feature lists without benefit connections - Impressive-sounding claims that don't land - Technical capabilities without outcomes - Company achievements that don't help the reader
Process: 1. Read each claim and literally ask "so what?" 2. Highlight claims missing the answer 3. Add the benefit bridge or deeper meaning 4. Ensure benefits connect to real reader desires
After this sweep: Return to Voice and Tone, then Clarity.
Focus: Is every claim supported with evidence?
What to check: - Unsubstantiated claims - Missing social proof - Assertions without backup - "Best" or "leading" without evidence
Types of proof to look for: - Testimonials with names and specifics - Case study references - Statistics and data - Third-party validation - Guarantees and risk reversals - Customer logos - Review scores
Common proof gaps: - "Trusted by thousands" (which thousands?) - "Industry-leading" (according to whom?) - "Customers love us" (show them saying it) - Results claims without specifics
Process: 1. Identify every claim that needs proof 2. Check if proof exists nearby 3. Flag unsupported assertions 4. Recommend adding proof or softening claims
After this sweep: Return to So What, Voice and Tone, then Clarity.
Focus: Is the copy concrete enough to be compelling?
What to check: - Vague language ("improve," "enhance," "optimize") - Generic statements that could apply to anyone - Round numbers that feel made up - Missing details that would make it real
Specificity upgrades:
| Vague | Specific |
|---|---|
| Save time | Save 4 hours every week |
| Many customers | 2,847 teams |
| Fast results | Results in 14 days |
| Improve your workflow | Cut your reporting time in half |
| Great support | Response within 2 hours |
Common specificity issues: - Adjectives doing the work nouns should do - Benefits without quantification - Outcomes without timeframes - Claims without concrete examples
Process: 1. Highlight vague words and phrases 2. Ask "Can this be more specific?" 3. Add numbers, timeframes, or examples 4. Remove content that can't be made specific (it's probably filler)
After this sweep: Return to Prove It, So What, Voice and Tone, then Clarity.
Focus: Does the copy make the reader feel something?
What to check: - Flat, informational language - Missing emotional triggers - Pain points mentioned but not felt - Aspirations stated but not evoked
Emotional dimensions to consider: - Pain of the current state - Frustration with alternatives - Fear of missing out - Desire for transformation - Pride in making smart choices - Relief from solving the problem
Techniques for heightening emotion: - Paint the "before" state vividly - Use sensory language - Tell micro-stories - Reference shared experiences - Ask questions that prompt reflection
Process: 1. Read for emotional impact—does it move you? 2. Identify flat sections that should resonate 3. Add emotional texture while staying authentic 4. Ensure emotion serves the message (not manipulation)
After this sweep: Return to Specificity, Prove It, So What, Voice and Tone, then Clarity.
Focus: Have we removed every barrier to action?
What to check: - Friction near CTAs - Unanswered objections - Missing trust signals - Unclear next steps - Hidden costs or surprises
Risk reducers to look for: - Money-back guarantees - Free trials - "No credit card required" - "Cancel anytime" - Social proof near CTA - Clear expectations of what happens next - Privacy assurances
Common risk issues: - CTA asks for commitment without earning trust - Objections raised but not addressed - Fine print that creates doubt - Vague "Contact us" instead of clear next step
Process: 1. Focus on sections near CTAs 2. List every reason someone might hesitate 3. Check if the copy addresses each concern 4. Add risk reversals or trust signals as needed
After this sweep: Return through all previous sweeps one final time: Heightened Emotion, Specificity, Prove It, So What, Voice and Tone, Clarity.
Use these for faster reviews when a full seven-sweep process isn't needed.
If the draft may be AI-generated (or AI-assisted), run the detector before editing:
python3 scripts/ai_content_detector.py draft.md --json # no arg = --demo mode
It scores burstiness, vocabulary diversity, and stock-phrase density. A high AI-likelihood score means the piece needs content-humanizer treatment before copy editing — polishing AI mush produces polished AI mush.
Cut these words: - Very, really, extremely, incredibly (weak intensifiers) - Just, actually, basically (filler) - In order to (use "to") - That (often unnecessary) - Things, stuff (vague)
Replace these:
| Weak | Strong |
|---|---|
| Utilize | Use |
| Implement | Set up |
| Leverage | Use |
| Facilitate | Help |
| Innovative | New |
| Robust | Strong |
| Seamless | Smooth |
| Cutting-edge | New/Modern |
Watch for: - Adverbs (usually unnecessary) - Passive voice (switch to active) - Nominalizations (verb → noun: "make a decision" → "decide")
Symptom: List of what the product does without why it matters Fix: Add "which means..." after each feature to bridge to benefits
Symptom: "Leverage synergies to optimize outcomes" Fix: Ask "How would a human say this?" and use those words
Symptom: Starting with company history or vague statements Fix: Lead with the reader's problem or desired outcome
Symptom: The ask comes after too much buildup, or isn't clear Fix: Make the CTA obvious, early, and repeated
Symptom: "Customers love us" with no evidence Fix: Add specific testimonials, numbers, or case references
Symptom: "We help businesses grow" Fix: Specify who, how, and by how much
Symptom: Copy tries to speak to everyone, resonates with no one Fix: Pick one audience and write directly to them
Symptom: Listing every capability, overwhelming the reader Fix: Focus on 3-5 key benefits that matter most to the audience
When editing collaboratively:
This iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.
| Task | Skill to Use |
|---|---|
| Writing new page copy from scratch | copywriting |
| Reviewing and improving existing copy | copy-editing (this skill) |
| Editing copy you just wrote | copy-editing (this skill) |
| Structural or strategic page changes | page-cro |
Surface these issues WITHOUT being asked when you notice them in context:
| When you ask for... | You get... |
|---|---|
| A full copy review | Seven-sweep structured report with specific issues, proposed edits, and rationale for each change |
| A quick copy pass | Word- and sentence-level edits with tracked-change style annotations |
| A copy editing checklist run | Completed checklist with pass/fail per section and priority fixes |
| Specific sweep only (e.g., Clarity) | Focused report for that sweep with before/after examples |
| Final polish | Clean edited version of the copy with a summary of all changes made |
All output follows the structured communication standard:
Deliver findings sweep-by-sweep. Don't dump all issues at once. Prioritize by conversion impact, not writing preference.
LICENSESKILL.mdreferences/ai-detection-patterns.mdreferences/plain-english-alternatives.mdscripts/ai_content_detector.pyscripts/readability_scorer.pyVendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path marketing-skill/skills/copy-editing, licence MIT. The upstream licence file ships inside the skill.