copy-editing▌
sickn33/antigravity-awesome-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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:
- Read through quickly, highlighting unclear parts
- Don't correct yet—just note problem areas
- After marking issues, recommend specific edits
- 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:
- Read aloud to hear inconsistencies
- Mark where tone shifts unexpectedly
- Recommend edits that smooth transitions
- 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:
- Read each claim and literally ask "so what?"
- Highlight claims missing the answer
- Add the benefit bridge or deeper meaning
- 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:
- Identify every claim that needs proof
- Check if proof exists nearby
- Flag unsupported assertions
- 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:
- Highlight vague words and phrases
- Ask "Can this be more specific?"
- Add numbers, timeframes, or examples
- 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 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:
- Read for emotional impact—does it move you?
- Identify flat sections that should resonate
- Add emotional texture while staying authentic
- Ensure emotion serves the message (not manipulation)
After this sweep: Return to Specificity, Prove It, So What, Voice and Tone, then Clarity.
Sweep 7: Zero Risk
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:
- Focus on sections near CTAs
- List every reason someone might hesitate
- Check if the copy addresses each concern
- 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.
Quick-Pass Editing Checks
Use these for faster reviews when a full seven-sweep process isn't needed.
Word-Level Checks
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")
Sentence-Level Checks
- One idea per sentence
- Vary sentence length (mix short and long)
- Front-load important information
- Max 3 conjunctions per sentence
- No more than 25 words (usually)
Paragraph-Level Checks
- One topic per paragraph
- Short paragraphs (2-4 sentences for web)
- Strong opening sentences
- Logical flow between paragraphs
- White space for scannability
Copy Editing Checklist
Before You Start
- Understand the goal of this copy
- Know the target audience
- Identify the desired action
- Read through once without editing
Clarity (Sweep 1)
- Every sentence is immediately understandable
- No jargon without explanation
- Pronouns have clear references
- No sentences trying to do too much
Voice & Tone (Sweep 2)
- Consistent formality level throughout
- Brand personality maintained
- No jarring shifts in mood
- Reads well aloud
So What (Sweep 3)
- Every feature connects to a benefit
- Claims answer "why should I care?"
- Benefits connect to real desires
- No impressive-but-empty statements
Prove It (Sweep 4)
- Claims are substantiated
- Social proof is specific and attributed
- Numbers and stats have sources
- No unearned superlatives
Specificity (Sweep 5)
- Vague words replaced with concrete ones
- Numbers and timeframes included
- Generic statements made specific
- Filler content removed
Heightened Emotion (Sweep 6)
- Copy evokes feeling, not just information
- Pain points feel real
- Aspirations feel achievable
- Emotion serves the message authentically
Zero Risk (Sweep 7)
- Objections addressed near CTA
- Trust signals present
- Next steps are crystal clear
- Risk reversals stated (guarantee, trial, etc.)
Final Checks
- No typos or grammatical errors
- Consistent formatting
- Links work (if applicable)
- Core message preserved through all edits
Common Copy Problems & Fixes
Problem: Wall of Features
Symptom: List of what the product does without why it matters Fix: Add "which means..." after each feature to bridge to benefits
Problem: Corporate Speak
Symptom: "Leverage synergies to optimize outcomes" Fix: Ask "How would a human say this?" and use those words
Problem: Weak Opening
Symptom: Starting with company history or vague statements Fix: Lead with the reader's problem or desired outcome
Problem: Buried CTA
Symptom: The ask comes after too much buildup, or isn't clear Fix: Make the CTA obvious, early, and repeated
Problem: No Proof
Symptom: "Customers love us" with no evidence Fix: Add specific testimonials, numbers, or case references
Problem: Generic Claims
Symptom: "We help businesses grow" Fix: Specify who, how, and by how much
Problem: Mixed Audiences
Symptom: Copy tries to speak to everyone, resonates with no one Fix: Pick one audience and write directly to them
Problem: Feature Overload
Symptom: Listing every capability, overwhelming the reader Fix: Focus on 3-5 key benefits that matter most to the audience
Working with Copy Sweeps
When editing collaboratively:
- Run a sweep and present findings - Show what you found, why it's an issue
- Recommend specific edits - Don't just identify problems; propose solutions
- Request the updated copy - Let the author make final decisions
- Verify previous sweeps - After each round of edits, re-check earlier sweeps
- Repeat until clean - Continue until a full sweep finds no new issues
This iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.
Questions to Ask
If you need more context:
- What's the goal of this copy? (Awareness, conversion, retention)
- Who's the target audience?
- What action should readers take?
- What's the brand voice? (Casual, professional, playful, authoritative)
- Are there specific concerns or known issues?
- What proof/evidence do you have available?
Related Skills
- copywriting: For writing new copy from scratch (use this skill to edit after your first draft is complete)
- page-cro: For broader page optimization beyond copy
- marketing-psychology: For understanding why certain edits improve conversion
- ab-test-setup: For testing copy variations
When to Use Each Skill
| 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 |
How to use copy-editing on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add copy-editing
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches copy-editing from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate copy-editing. Access the skill through slash commands (e.g., /copy-editing) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★66 reviews- ★★★★★Hassan Okafor· Dec 28, 2024
We added copy-editing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sophia Srinivasan· Dec 20, 2024
copy-editing has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ren Kim· Dec 12, 2024
copy-editing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Amelia Jain· Dec 4, 2024
copy-editing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Alexander Huang· Nov 23, 2024
copy-editing has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zara Sanchez· Nov 19, 2024
Solid pick for teams standardizing on skills: copy-editing is focused, and the summary matches what you get after install.
- ★★★★★Alexander Patel· Nov 11, 2024
copy-editing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hassan Diallo· Nov 3, 2024
copy-editing reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Noor Gonzalez· Oct 22, 2024
Registry listing for copy-editing matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Arjun Khan· Oct 14, 2024
Solid pick for teams standardizing on skills: copy-editing is focused, and the summary matches what you get after install.
showing 1-10 of 66