[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFMP97FHEDRBYVRGYP2HWG":3,"skill-same:01M6MFMP97FHEDRBYVRGYP2HWG":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":13,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6MFMP97FHEDRBYVRGYP2HWG","copy-editing",null,"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.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-copy-editing-skill-03d405e2\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"copy editing","copy","editing","Existing","review","my","make","systematic","proofread","use","user","edit","sweep","feedback","marketing","polish","improve","2026-11-10 10:12:30",false,"---\nname: \"copy-editing\"\ndescription: \"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.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Copy Editing\n\nYou 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.\n\n## Core Philosophy\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before editing. Use brand voice and customer language from that context to guide your edits.\n\nGood 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.\n\n**Key principles:**\n- Don't change the core message; focus on enhancing it\n- Multiple focused passes beat one unfocused review\n- Each edit should have a clear reason\n- Preserve the author's voice while improving clarity\n\n---\n\n## The Seven Sweeps Framework\n\nEdit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised.\n\n### Sweep 1: Clarity\n\n**Focus:** Can the reader understand what you're saying?\n\n**What to check:**\n- Confusing sentence structures\n- Unclear pronoun references\n- Jargon or insider language\n- Ambiguous statements\n- Missing context\n\n**Common clarity killers:**\n- Sentences trying to say too much\n- Abstract language instead of concrete\n- Assuming reader knowledge they don't have\n- Burying the point in qualifications\n\n**Process:**\n1. Score the draft mechanically first: `python3 scripts\u002Freadability_scorer.py --file draft.md` (Flesch score, passive-voice %, filler-word count; add `--json` for pipelines). Anything it flags is your starting highlight list.\n2. Read through quickly, highlighting unclear parts the scorer can't see\n3. Don't correct yet—just note problem areas\n4. After marking issues, recommend specific edits\n5. Verify edits maintain the original intent — re-run the scorer; the Flesch score should improve, not regress\n\n**After this sweep:** Confirm the \"Rule of One\" (one main idea per section) and \"You Rule\" (copy speaks to the reader) are intact.\n\n---\n\n### Sweep 2: Voice and Tone\n\n**Focus:** Is the copy consistent in how it sounds?\n\n**What to check:**\n- Shifts between formal and casual\n- Inconsistent brand personality\n- Mood changes that feel jarring\n- Word choices that don't match the brand\n\n**Common voice issues:**\n- Starting casual, becoming corporate\n- Mixing \"we\" and \"the company\" references\n- Humor in some places, serious in others (unintentionally)\n- Technical language appearing randomly\n\n**Process:**\n1. Read aloud to hear inconsistencies\n2. Mark where tone shifts unexpectedly\n3. Recommend edits that smooth transitions\n4. Ensure personality remains throughout\n\n**After this sweep:** Return to Clarity Sweep to ensure voice edits didn't introduce confusion.\n\n---\n\n### Sweep 3: So What\n\n**Focus:** Does every claim answer \"why should I care?\"\n\n**What to check:**\n- Features without benefits\n- Claims without consequences\n- Statements that don't connect to reader's life\n- Missing \"which means...\" bridges\n\n**The So What test:**\nFor every statement, ask \"Okay, so what?\" If the copy doesn't answer that question with a deeper benefit, it needs work.\n\n❌ \"Our platform uses AI-powered analytics\"\n*So what?*\n✅ \"Our AI-powered analytics surface insights you'd miss manually—so you can make better decisions in half the time\"\n\n**Common So What failures:**\n- Feature lists without benefit connections\n- Impressive-sounding claims that don't land\n- Technical capabilities without outcomes\n- Company achievements that don't help the reader\n\n**Process:**\n1. Read each claim and literally ask \"so what?\"\n2. Highlight claims missing the answer\n3. Add the benefit bridge or deeper meaning\n4. Ensure benefits connect to real reader desires\n\n**After this sweep:** Return to Voice and Tone, then Clarity.\n\n---\n\n### Sweep 4: Prove It\n\n**Focus:** Is every claim supported with evidence?\n\n**What to check:**\n- Unsubstantiated claims\n- Missing social proof\n- Assertions without backup\n- \"Best\" or \"leading\" without evidence\n\n**Types of proof to look for:**\n- Testimonials with names and specifics\n- Case study references\n- Statistics and data\n- Third-party validation\n- Guarantees and risk reversals\n- Customer logos\n- Review scores\n\n**Common proof gaps:**\n- \"Trusted by thousands\" (which thousands?)\n- \"Industry-leading\" (according to whom?)\n- \"Customers love us\" (show them saying it)\n- Results claims without specifics\n\n**Process:**\n1. Identify every claim that needs proof\n2. Check if proof exists nearby\n3. Flag unsupported assertions\n4. Recommend adding proof or softening claims\n\n**After this sweep:** Return to So What, Voice and Tone, then Clarity.\n\n---\n\n### Sweep 5: Specificity\n\n**Focus:** Is the copy concrete enough to be compelling?\n\n**What to check:**\n- Vague language (\"improve,\" \"enhance,\" \"optimize\")\n- Generic statements that could apply to anyone\n- Round numbers that feel made up\n- Missing details that would make it real\n\n**Specificity upgrades:**\n\n| Vague | Specific |\n|-------|----------|\n| Save time | Save 4 hours every week |\n| Many customers | 2,847 teams |\n| Fast results | Results in 14 days |\n| Improve your workflow | Cut your reporting time in half |\n| Great support | Response within 2 hours |\n\n**Common specificity issues:**\n- Adjectives doing the work nouns should do\n- Benefits without quantification\n- Outcomes without timeframes\n- Claims without concrete examples\n\n**Process:**\n1. Highlight vague words and phrases\n2. Ask \"Can this be more specific?\"\n3. Add numbers, timeframes, or examples\n4. Remove content that can't be made specific (it's probably filler)\n\n**After this sweep:** Return to Prove It, So What, Voice and Tone, then Clarity.\n\n---\n\n### Sweep 6: Heightened Emotion\n\n**Focus:** Does the copy make the reader feel something?\n\n**What to check:**\n- Flat, informational language\n- Missing emotional triggers\n- Pain points mentioned but not felt\n- Aspirations stated but not evoked\n\n**Emotional dimensions to consider:**\n- Pain of the current state\n- Frustration with alternatives\n- Fear of missing out\n- Desire for transformation\n- Pride in making smart choices\n- Relief from solving the problem\n\n**Techniques for heightening emotion:**\n- Paint the \"before\" state vividly\n- Use sensory language\n- Tell micro-stories\n- Reference shared experiences\n- Ask questions that prompt reflection\n\n**Process:**\n1. Read for emotional impact—does it move you?\n2. Identify flat sections that should resonate\n3. Add emotional texture while staying authentic\n4. Ensure emotion serves the message (not manipulation)\n\n**After this sweep:** Return to Specificity, Prove It, So What, Voice and Tone, then Clarity.\n\n---\n\n### Sweep 7: Zero Risk\n\n**Focus:** Have we removed every barrier to action?\n\n**What to check:**\n- Friction near CTAs\n- Unanswered objections\n- Missing trust signals\n- Unclear next steps\n- Hidden costs or surprises\n\n**Risk reducers to look for:**\n- Money-back guarantees\n- Free trials\n- \"No credit card required\"\n- \"Cancel anytime\"\n- Social proof near CTA\n- Clear expectations of what happens next\n- Privacy assurances\n\n**Common risk issues:**\n- CTA asks for commitment without earning trust\n- Objections raised but not addressed\n- Fine print that creates doubt\n- Vague \"Contact us\" instead of clear next step\n\n**Process:**\n1. Focus on sections near CTAs\n2. List every reason someone might hesitate\n3. Check if the copy addresses each concern\n4. Add risk reversals or trust signals as needed\n\n**After this sweep:** Return through all previous sweeps one final time: Heightened Emotion, Specificity, Prove It, So What, Voice and Tone, Clarity.\n\n---\n\n## Quick-Pass Editing Checks\n\nUse these for faster reviews when a full seven-sweep process isn't needed.\n\n### AI-Pattern Check\n\nIf the draft may be AI-generated (or AI-assisted), run the detector before editing:\n\n```bash\npython3 scripts\u002Fai_content_detector.py draft.md --json   # no arg = --demo mode\n```\n\nIt 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.\n\n### Word-Level Checks\n\n**Cut these words:**\n- Very, really, extremely, incredibly (weak intensifiers)\n- Just, actually, basically (filler)\n- In order to (use \"to\")\n- That (often unnecessary)\n- Things, stuff (vague)\n\n**Replace these:**\n\n| Weak | Strong |\n|------|--------|\n| Utilize | Use |\n| Implement | Set up |\n| Leverage | Use |\n| Facilitate | Help |\n| Innovative | New |\n| Robust | Strong |\n| Seamless | Smooth |\n| Cutting-edge | New\u002FModern |\n\n**Watch for:**\n- Adverbs (usually unnecessary)\n- Passive voice (switch to active)\n- Nominalizations (verb → noun: \"make a decision\" → \"decide\")\n\n### Sentence-Level Checks\n\n- One idea per sentence\n- Vary sentence length (mix short and long)\n- Front-load important information\n- Max 3 conjunctions per sentence\n- No more than 25 words (usually)\n\n### Paragraph-Level Checks\n\n- One topic per paragraph\n- Short paragraphs (2-4 sentences for web)\n- Strong opening sentences\n- Logical flow between paragraphs\n- White space for scannability\n\n---\n\n## Copy Editing Checklist\n\n### Before You Start\n- [ ] Understand the goal of this copy\n- [ ] Know the target audience\n- [ ] Identify the desired action\n- [ ] Read through once without editing\n\n### Clarity (Sweep 1)\n- [ ] Every sentence is immediately understandable\n- [ ] No jargon without explanation\n- [ ] Pronouns have clear references\n- [ ] No sentences trying to do too much\n\n### Voice & Tone (Sweep 2)\n- [ ] Consistent formality level throughout\n- [ ] Brand personality maintained\n- [ ] No jarring shifts in mood\n- [ ] Reads well aloud\n\n### So What (Sweep 3)\n- [ ] Every feature connects to a benefit\n- [ ] Claims answer \"why should I care?\"\n- [ ] Benefits connect to real desires\n- [ ] No impressive-but-empty statements\n\n### Prove It (Sweep 4)\n- [ ] Claims are substantiated\n- [ ] Social proof is specific and attributed\n- [ ] Numbers and stats have sources\n- [ ] No unearned superlatives\n\n### Specificity (Sweep 5)\n- [ ] Vague words replaced with concrete ones\n- [ ] Numbers and timeframes included\n- [ ] Generic statements made specific\n- [ ] Filler content removed\n\n### Heightened Emotion (Sweep 6)\n- [ ] Copy evokes feeling, not just information\n- [ ] Pain points feel real\n- [ ] Aspirations feel achievable\n- [ ] Emotion serves the message authentically\n\n### Zero Risk (Sweep 7)\n- [ ] Objections addressed near CTA\n- [ ] Trust signals present\n- [ ] Next steps are crystal clear\n- [ ] Risk reversals stated (guarantee, trial, etc.)\n\n### Final Checks\n- [ ] No typos or grammatical errors\n- [ ] Consistent formatting\n- [ ] Links work (if applicable)\n- [ ] Core message preserved through all edits\n\n---\n\n## Common Copy Problems & Fixes\n\n### Problem: Wall of Features\n**Symptom:** List of what the product does without why it matters\n**Fix:** Add \"which means...\" after each feature to bridge to benefits\n\n### Problem: Corporate Speak\n**Symptom:** \"Leverage synergies to optimize outcomes\"\n**Fix:** Ask \"How would a human say this?\" and use those words\n\n### Problem: Weak Opening\n**Symptom:** Starting with company history or vague statements\n**Fix:** Lead with the reader's problem or desired outcome\n\n### Problem: Buried CTA\n**Symptom:** The ask comes after too much buildup, or isn't clear\n**Fix:** Make the CTA obvious, early, and repeated\n\n### Problem: No Proof\n**Symptom:** \"Customers love us\" with no evidence\n**Fix:** Add specific testimonials, numbers, or case references\n\n### Problem: Generic Claims\n**Symptom:** \"We help businesses grow\"\n**Fix:** Specify who, how, and by how much\n\n### Problem: Mixed Audiences\n**Symptom:** Copy tries to speak to everyone, resonates with no one\n**Fix:** Pick one audience and write directly to them\n\n### Problem: Feature Overload\n**Symptom:** Listing every capability, overwhelming the reader\n**Fix:** Focus on 3-5 key benefits that matter most to the audience\n\n---\n\n## Working with Copy Sweeps\n\nWhen editing collaboratively:\n\n1. **Run a sweep and present findings** - Show what you found, why it's an issue\n2. **Recommend specific edits** - Don't just identify problems; propose solutions\n3. **Request the updated copy** - Let the author make final decisions\n4. **Verify previous sweeps** - After each round of edits, re-check earlier sweeps\n5. **Repeat until clean** - Continue until a full sweep finds no new issues\n\nThis iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.\n\n---\n\n## References\n\n- [Plain English Alternatives](references\u002Fplain-english-alternatives.md): Replace complex words with simpler alternatives\n\n---\n\n## Task-Specific Questions\n\n1. What's the goal of this copy? (Awareness, conversion, retention)\n2. What action should readers take?\n3. Are there specific concerns or known issues?\n4. What proof\u002Fevidence do you have available?\n\n---\n\n## When to Use Each Skill\n\n| Task | Skill to Use |\n|------|--------------|\n| Writing new page copy from scratch | copywriting |\n| Reviewing and improving existing copy | copy-editing (this skill) |\n| Editing copy you just wrote | copy-editing (this skill) |\n| Structural or strategic page changes | page-cro |\n\n---\n\n## Proactive Triggers\n\nSurface these issues WITHOUT being asked when you notice them in context:\n\n- **Copy is submitted for editing without a stated goal** → Ask for the target action and audience before starting any sweeps; editing without this context guarantees misaligned feedback.\n- **Multiple tone shifts detected** → Flag Sweep 2 failure immediately; note the specific lines where voice breaks and propose fixes before continuing.\n- **Features outnumber benefits 2:1 or more** → Raise the \"So What\" alarm early in the review; this is the single most common conversion killer.\n- **Superlatives without proof** (\"best,\" \"leading,\" \"most trusted\") → Flag each instance in Sweep 4 and request the evidence or softer language alternatives.\n- **CTA is vague or buried** → Call this out in Sweep 7 before delivering any other feedback — it's the highest-impact fix.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| A full copy review | Seven-sweep structured report with specific issues, proposed edits, and rationale for each change |\n| A quick copy pass | Word- and sentence-level edits with tracked-change style annotations |\n| A copy editing checklist run | Completed checklist with pass\u002Ffail per section and priority fixes |\n| Specific sweep only (e.g., Clarity) | Focused report for that sweep with before\u002Fafter examples |\n| Final polish | Clean edited version of the copy with a summary of all changes made |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n\n- **Bottom line first** — state the overall copy health before diving into issues\n- **What + Why + How** — every flagged issue gets: what's wrong, why it hurts conversion, how to fix it\n- **Edits have reasons** — never change words without explaining the principle\n- **Confidence tagging** — ? clear improvement \u002F ? judgment call \u002F ? needs author input\n\nDeliver findings sweep-by-sweep. Don't dump all issues at once. Prioritize by conversion impact, not writing preference.\n\n---\n\n## Related Skills\n\n- **marketing-context**: USE as foundation before editing — provides brand voice, ICP, and tone benchmarks. NOT a substitute for reading the copy itself.\n- **copywriting**: USE when the copy needs to be rewritten from scratch rather than edited. NOT for polishing existing drafts.\n- **content-strategy**: USE when the problem is what to say, not how to say it. NOT for line-level improvements.\n- **social-content**: USE when edited copy needs to be adapted for social platforms. NOT for page-level editing.\n- **marketing-ideas**: USE when the client needs a new marketing angle entirely. NOT for editorial improvement.\n- **content-humanizer**: USE when AI-generated copy needs to pass the human test before copy editing begins. NOT for structural review.\n- **ab-test-setup**: USE when disagreement on copy variants needs data to resolve. NOT for the editing process itself.\n","# Copy Editing\n\nYou 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.\n\n## Core Philosophy\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before editing. Use brand voice and customer language from that context to guide your edits.\n\nGood 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.\n\n**Key principles:**\n- Don't change the core message; focus on enhancing it\n- Multiple focused passes beat one unfocused review\n- Each edit should have a clear reason\n- Preserve the author's voice while improving clarity\n\n---\n\n## The Seven Sweeps Framework\n\nEdit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised.\n\n### Sweep 1: Clarity\n\n**Focus:** Can the reader understand what you're saying?\n\n**What to check:**\n- Confusing sentence structures\n- Unclear pronoun references\n- Jargon or insider language\n- Ambiguous statements\n- Missing context\n\n**Common clarity killers:**\n- Sentences trying to say too much\n- Abstract language instead of concrete\n- Assuming reader knowledge they don't have\n- Burying the point in qualifications\n\n**Process:**\n1. Score the draft mechanically first: `python3 scripts\u002Freadability_scorer.py --file draft.md` (Flesch score, passive-voice %, filler-word count; add `--json` for pipelines). Anything it flags is your starting highlight list.\n2. Read through quickly, highlighting unclear parts the scorer can't see\n3. Don't correct yet—just note problem areas\n4. After marking issues, recommend specific edits\n5. Verify edits maintain the original intent — re-run the scorer; the Flesch score should improve, not regress\n\n**After this sweep:** Confirm the \"Rule of One\" (one main idea per section) and \"You Rule\" (copy speaks to the reader) are intact.\n\n---\n\n### Sweep 2: Voice and Tone\n\n**Focus:** Is the copy consistent in how it sounds?\n\n**What to check:**\n- Shifts between formal and casual\n- Inconsistent brand personality\n- Mood changes that feel jarring\n- Word choices that don't match the brand\n\n**Common voice issues:**\n- Starting casual, becoming corporate\n- Mixing \"we\" and \"the company\" references\n- Humor in some places, serious in others (unintentionally)\n- Technical language appearing randomly\n\n**Process:**\n1. Read aloud to hear inconsistencies\n2. Mark where tone shifts unexpectedly\n3. Recommend edits that smooth transitions\n4. Ensure personality remains throughout\n\n**After this sweep:** Return to Clarity Sweep to ensure voice edits didn't introduce confusion.\n\n---\n\n### Sweep 3: So What\n\n**Focus:** Does every claim answer \"why should I care?\"\n\n**What to check:**\n- Features without benefits\n- Claims without consequences\n- Statements that don't connect to reader's life\n- Missing \"which means...\" bridges\n\n**The So What test:**\nFor every statement, ask \"Okay, so what?\" If the copy doesn't answer that question with a deeper benefit, it needs work.\n\n❌ \"Our platform uses AI-powered analytics\"\n*So what?*\n✅ \"Our AI-powered analytics surface insights you'd miss manually—so you can make better decisions in half the time\"\n\n**Common So What failures:**\n- Feature lists without benefit connections\n- Impressive-sounding claims that don't land\n- Technical capabilities without outcomes\n- Company achievements that don't help the reader\n\n**Process:**\n1. Read each claim and literally ask \"so what?\"\n2. Highlight claims missing the answer\n3. Add the benefit bridge or deeper meaning\n4. Ensure benefits connect to real reader desires\n\n**After this sweep:** Return to Voice and Tone, then Clarity.\n\n---\n\n### Sweep 4: Prove It\n\n**Focus:** Is every claim supported with evidence?\n\n**What to check:**\n- Unsubstantiated claims\n- Missing social proof\n- Assertions without backup\n- \"Best\" or \"leading\" without evidence\n\n**Types of proof to look for:**\n- Testimonials with names and specifics\n- Case study references\n- Statistics and data\n- Third-party validation\n- Guarantees and risk reversals\n- Customer logos\n- Review scores\n\n**Common proof gaps:**\n- \"Trusted by thousands\" (which thousands?)\n- \"Industry-leading\" (according to whom?)\n- \"Customers love us\" (show them saying it)\n- Results claims without specifics\n\n**Process:**\n1. Identify every claim that needs proof\n2. Check if proof exists nearby\n3. Flag unsupported assertions\n4. Recommend adding proof or softening claims\n\n**After this sweep:** Return to So What, Voice and Tone, then Clarity.\n\n---\n\n### Sweep 5: Specificity\n\n**Focus:** Is the copy concrete enough to be compelling?\n\n**What to check:**\n- Vague language (\"improve,\" \"enhance,\" \"optimize\")\n- Generic statements that could apply to anyone\n- Round numbers that feel made up\n- Missing details that would make it real\n\n**Specificity upgrades:**\n\n| Vague | Specific |\n|-------|----------|\n| Save time | Save 4 hours every week |\n| Many customers | 2,847 teams |\n| Fast results | Results in 14 days |\n| Improve your workflow | Cut your reporting time in half |\n| Great support | Response within 2 hours |\n\n**Common specificity issues:**\n- Adjectives doing the work nouns should do\n- Benefits without quantification\n- Outcomes without timeframes\n- Claims without concrete examples\n\n**Process:**\n1. Highlight vague words and phrases\n2. Ask \"Can this be more specific?\"\n3. Add numbers, timeframes, or examples\n4. Remove content that can't be made specific (it's probably filler)\n\n**After this sweep:** Return to Prove It, So What, Voice and Tone, then Clarity.\n\n---\n\n### Sweep 6: Heightened Emotion\n\n**Focus:** Does the copy make the reader feel something?\n\n**What to check:**\n- Flat, informational language\n- Missing emotional triggers\n- Pain points mentioned but not felt\n- Aspirations stated but not evoked\n\n**Emotional dimensions to consider:**\n- Pain of the current state\n- Frustration with alternatives\n- Fear of missing out\n- Desire for transformation\n- Pride in making smart choices\n- Relief from solving the problem\n\n**Techniques for heightening emotion:**\n- Paint the \"before\" state vividly\n- Use sensory language\n- Tell micro-stories\n- Reference shared experiences\n- Ask questions that prompt reflection\n\n**Process:**\n1. Read for emotional impact—does it move you?\n2. Identify flat sections that should resonate\n3. Add emotional texture while staying authentic\n4. Ensure emotion serves the message (not manipulation)\n\n**After this sweep:** Return to Specificity, Prove It, So What, Voice and Tone, then Clarity.\n\n---\n\n### Sweep 7: Zero Risk\n\n**Focus:** Have we removed every barrier to action?\n\n**What to check:**\n- Friction near CTAs\n- Unanswered objections\n- Missing trust signals\n- Unclear next steps\n- Hidden costs or surprises\n\n**Risk reducers to look for:**\n- Money-back guarantees\n- Free trials\n- \"No credit card required\"\n- \"Cancel anytime\"\n- Social proof near CTA\n- Clear expectations of what happens next\n- Privacy assurances\n\n**Common risk issues:**\n- CTA asks for commitment without earning trust\n- Objections raised but not addressed\n- Fine print that creates doubt\n- Vague \"Contact us\" instead of clear next step\n\n**Process:**\n1. Focus on sections near CTAs\n2. List every reason someone might hesitate\n3. Check if the copy addresses each concern\n4. Add risk reversals or trust signals as needed\n\n**After this sweep:** Return through all previous sweeps one final time: Heightened Emotion, Specificity, Prove It, So What, Voice and Tone, Clarity.\n\n---\n\n## Quick-Pass Editing Checks\n\nUse these for faster reviews when a full seven-sweep process isn't needed.\n\n### AI-Pattern Check\n\nIf the draft may be AI-generated (or AI-assisted), run the detector before editing:\n\n```bash\npython3 scripts\u002Fai_content_detector.py draft.md --json   # no arg = --demo mode\n```\n\nIt 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.\n\n### Word-Level Checks\n\n**Cut these words:**\n- Very, really, extremely, incredibly (weak intensifiers)\n- Just, actually, basically (filler)\n- In order to (use \"to\")\n- That (often unnecessary)\n- Things, stuff (vague)\n\n**Replace these:**\n\n| Weak | Strong |\n|------|--------|\n| Utilize | Use |\n| Implement | Set up |\n| Leverage | Use |\n| Facilitate | Help |\n| Innovative | New |\n| Robust | Strong |\n| Seamless | Smooth |\n| Cutting-edge | New\u002FModern |\n\n**Watch for:**\n- Adverbs (usually unnecessary)\n- Passive voice (switch to active)\n- Nominalizations (verb → noun: \"make a decision\" → \"decide\")\n\n### Sentence-Level Checks\n\n- One idea per sentence\n- Vary sentence length (mix short and long)\n- Front-load important information\n- Max 3 conjunctions per sentence\n- No more than 25 words (usually)\n\n### Paragraph-Level Checks\n\n- One topic per paragraph\n- Short paragraphs (2-4 sentences for web)\n- Strong opening sentences\n- Logical flow between paragraphs\n- White space for scannability\n\n---\n\n## Copy Editing Checklist\n\n### Before You Start\n- [ ] Understand the goal of this copy\n- [ ] Know the target audience\n- [ ] Identify the desired action\n- [ ] Read through once without editing\n\n### Clarity (Sweep 1)\n- [ ] Every sentence is immediately understandable\n- [ ] No jargon without explanation\n- [ ] Pronouns have clear references\n- [ ] No sentences trying to do too much\n\n### Voice & Tone (Sweep 2)\n- [ ] Consistent formality level throughout\n- [ ] Brand personality maintained\n- [ ] No jarring shifts in mood\n- [ ] Reads well aloud\n\n### So What (Sweep 3)\n- [ ] Every feature connects to a benefit\n- [ ] Claims answer \"why should I care?\"\n- [ ] Benefits connect to real desires\n- [ ] No impressive-but-empty statements\n\n### Prove It (Sweep 4)\n- [ ] Claims are substantiated\n- [ ] Social proof is specific and attributed\n- [ ] Numbers and stats have sources\n- [ ] No unearned superlatives\n\n### Specificity (Sweep 5)\n- [ ] Vague words replaced with concrete ones\n- [ ] Numbers and timeframes included\n- [ ] Generic statements made specific\n- [ ] Filler content removed\n\n### Heightened Emotion (Sweep 6)\n- [ ] Copy evokes feeling, not just information\n- [ ] Pain points feel real\n- [ ] Aspirations feel achievable\n- [ ] Emotion serves the message authentically\n\n### Zero Risk (Sweep 7)\n- [ ] Objections addressed near CTA\n- [ ] Trust signals present\n- [ ] Next steps are crystal clear\n- [ ] Risk reversals stated (guarantee, trial, etc.)\n\n### Final Checks\n- [ ] No typos or grammatical errors\n- [ ] Consistent formatting\n- [ ] Links work (if applicable)\n- [ ] Core message preserved through all edits\n\n---\n\n## Common Copy Problems & Fixes\n\n### Problem: Wall of Features\n**Symptom:** List of what the product does without why it matters\n**Fix:** Add \"which means...\" after each feature to bridge to benefits\n\n### Problem: Corporate Speak\n**Symptom:** \"Leverage synergies to optimize outcomes\"\n**Fix:** Ask \"How would a human say this?\" and use those words\n\n### Problem: Weak Opening\n**Symptom:** Starting with company history or vague statements\n**Fix:** Lead with the reader's problem or desired outcome\n\n### Problem: Buried CTA\n**Symptom:** The ask comes after too much buildup, or isn't clear\n**Fix:** Make the CTA obvious, early, and repeated\n\n### Problem: No Proof\n**Symptom:** \"Customers love us\" with no evidence\n**Fix:** Add specific testimonials, numbers, or case references\n\n### Problem: Generic Claims\n**Symptom:** \"We help businesses grow\"\n**Fix:** Specify who, how, and by how much\n\n### Problem: Mixed Audiences\n**Symptom:** Copy tries to speak to everyone, resonates with no one\n**Fix:** Pick one audience and write directly to them\n\n### Problem: Feature Overload\n**Symptom:** Listing every capability, overwhelming the reader\n**Fix:** Focus on 3-5 key benefits that matter most to the audience\n\n---\n\n## Working with Copy Sweeps\n\nWhen editing collaboratively:\n\n1. **Run a sweep and present findings** - Show what you found, why it's an issue\n2. **Recommend specific edits** - Don't just identify problems; propose solutions\n3. **Request the updated copy** - Let the author make final decisions\n4. **Verify previous sweeps** - After each round of edits, re-check earlier sweeps\n5. **Repeat until clean** - Continue until a full sweep finds no new issues\n\nThis iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.\n\n---\n\n## References\n\n- [Plain English Alternatives](references\u002Fplain-english-alternatives.md): Replace complex words with simpler alternatives\n\n---\n\n## Task-Specific Questions\n\n1. What's the goal of this copy? (Awareness, conversion, retention)\n2. What action should readers take?\n3. Are there specific concerns or known issues?\n4. What proof\u002Fevidence do you have available?\n\n---\n\n## When to Use Each Skill\n\n| Task | Skill to Use |\n|------|--------------|\n| Writing new page copy from scratch | copywriting |\n| Reviewing and improving existing copy | copy-editing (this skill) |\n| Editing copy you just wrote | copy-editing (this skill) |\n| Structural or strategic page changes | page-cro |\n\n---\n\n## Proactive Triggers\n\nSurface these issues WITHOUT being asked when you notice them in context:\n\n- **Copy is submitted for editing without a stated goal** → Ask for the target action and audience before starting any sweeps; editing without this context guarantees misaligned feedback.\n- **Multiple tone shifts detected** → Flag Sweep 2 failure immediately; note the specific lines where voice breaks and propose fixes before continuing.\n- **Features outnumber benefits 2:1 or more** → Raise the \"So What\" alarm early in the review; this is the single most common conversion killer.\n- **Superlatives without proof** (\"best,\" \"leading,\" \"most trusted\") → Flag each instance in Sweep 4 and request the evidence or softer language alternatives.\n- **CTA is vague or buried** → Call this out in Sweep 7 before delivering any other feedback — it's the highest-impact fix.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| A full copy review | Seven-sweep structured report with specific issues, proposed edits, and rationale for each change |\n| A quick copy pass | Word- and sentence-level edits with tracked-change style annotations |\n| A copy editing checklist run | Completed checklist with pass\u002Ffail per section and priority fixes |\n| Specific sweep only (e.g., Clarity) | Focused report for that sweep with before\u002Fafter examples |\n| Final polish | Clean edited version of the copy with a summary of all changes made |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n\n- **Bottom line first** — state the overall copy health before diving into issues\n- **What + Why + How** — every flagged issue gets: what's wrong, why it hurts conversion, how to fix it\n- **Edits have reasons** — never change words without explaining the principle\n- **Confidence tagging** — ? clear improvement \u002F ? judgment call \u002F ? needs author input\n\nDeliver findings sweep-by-sweep. Don't dump all issues at once. Prioritize by conversion impact, not writing preference.\n\n---\n\n## Related Skills\n\n- **marketing-context**: USE as foundation before editing — provides brand voice, ICP, and tone benchmarks. NOT a substitute for reading the copy itself.\n- **copywriting**: USE when the copy needs to be rewritten from scratch rather than edited. NOT for polishing existing drafts.\n- **content-strategy**: USE when the problem is what to say, not how to say it. NOT for line-level improvements.\n- **social-content**: USE when edited copy needs to be adapted for social platforms. NOT for page-level editing.\n- **marketing-ideas**: USE when the client needs a new marketing angle entirely. NOT for editorial improvement.\n- **content-humanizer**: USE when AI-generated copy needs to pass the human test before copy editing begins. NOT for structural review.\n- **ab-test-setup**: USE when disagreement on copy variants needs data to resolve. NOT for the editing process itself.\n",{"name":5,"license":14,"metadata":50,"description":7},{"author":51,"updated":52,"version":53,"category":42},"Alireza Rezvani",1772755200000,"1.0.0","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-copy-editing-skill-03d405e2","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill copy-editing",{"tool":66,"command":67},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill copy-editing",{"tool":69,"command":70},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill copy-editing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-copy-editing-skill-03d405e2\u002FSKILL.md",true,[],[75,100,127,158,186,219],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":45},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[77,82,83,84,85,86,87,88,89,90,91,92,93,37,94,95,96,97,98,99],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","for","webmcp",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":45},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,33,125,126],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","at","copilot instructions",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":139,"publishedAt":45},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":137,"categoryName":138,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,141,142,143,144,145,146,147,148,149,150,151,152,37,153,154,155,156,98,157],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":45},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[168,169,170,171,172,173,174,175,176,37,177,178,179,180,181,182,183,184,185,98],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":201,"publishedAt":45},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[192,195,198],{"categoryNo":193,"categoryName":194,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":196,"categoryName":197,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":199,"categoryName":200,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[202,203,204,205,206,207,208,209,109,210,37,211,212,213,214,215,216,217,98,218],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":225,"publishedAt":45},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[226,227,228,229,230,205,231,37,215,232,233,234,235,236,237,238,239,240,98,241],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]