Skip to content
Development
Skill

/copy-editing

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing

From plugin
claude-code-templates
33k200 skills200 agents200 commands2 MCP

Claude Code

$ npx -y skills add davila7/claude-code-templates --skill copy-editing --agent claude-code

SKILL.md

copy-editing.SKILL.md
name: copy-editing
description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes."

Copy Editing

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.

Core Philosophy

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

---

The Seven Sweeps Framework

Edit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised.

Sweep 1: Clarity

**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. Read through quickly, highlighting unclear parts 2. Don't correct yet—just note problem areas 3. After marking issues, recommend specific edits 4. Verify edits maintain the original intent

**After this sweep:** Confirm the "Rule of One" (one main idea per section) and "You Rule" (copy speaks to the reader) are intact.

---

Sweep 2: Voice and Tone

**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.

---

Sweep 3: So What

**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.

---

Sweep 4: Prove It

**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.

---

Sweep 5: Specificity

**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.

---

Sweep 6: Heightened Emotion

**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
Read more
@davila7
Ships withclaude-code-templates

Open-source registry and CLI for Claude Code components: agents, commands, skills, hooks, MCPs, settings and mods

33k200 skills200 agents2 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
33.4k
Star history of davila7/claude-code-templates on GitHub, a chart by star-history.com

Other skills on claude-code-templates.

planning

planning

Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan",…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills12d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react3d252k
@facebook@facebookInstall Skill

Questions about copy-editing.

Which coding agents can use copy-editing?
copy-editing installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.