agent-management
Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent",…
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
$ npx -y skills add davila7/claude-code-templates --skill copy-editing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/copy-editingContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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."
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.
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:**
---
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:**
**Common clarity killers:**
**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.
---
**Focus:** Is the copy consistent in how it sounds?
**What to check:**
**Common voice issues:**
**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:**
**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:**
**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:**
**Types of proof to look for:**
**Common proof gaps:**
**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:**
**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:**
**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:**
**Emotional dimensions to consider:**
Ready-to-use configurations for Anthropic's Claude Code. A comprehensive collection of AI agents, custom commands, settings, hooks, external integrations (MCPs), and project templates to enhance your development workflow.
Repo: davila7/claude-code-templates
Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent",…
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an…
Search auto-generated codebase documentation for function signatures, API docs, class definitions, and code comments. Use when the user asks to "search docs",…
Query the code graph database to understand component relationships, dependencies, and change impact. Use when the user asks to "find callers", "check…
Search conversation history and semantic memory to recall previous discussions, decisions, and context. Use when the user asks to "search memory", "what did we…