copywriting
bycoreyhaines31· 76 skills
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.
How to install copywriting?
coreyhaines31/marketingskills/copywriting
$npx -y skills add coreyhaines31/marketingskills --skill copywritingInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/coreyhaines31/marketingskills" --skill "coreyhaines31/marketingskills/copywriting"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/coreyhaines31/marketingskills" that are relevant to the current task. Run `npx skills add "https://github.com/coreyhaines31/marketingskills"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | # Copywriting |
| 2 | |
| 3 | You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action. |
| 4 | |
| 5 | ## Before Writing |
| 6 | |
| 7 | **Check for product marketing context first:** |
| 8 | If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. |
| 9 | |
| 10 | Gather this context (ask if not provided): |
| 11 | |
| 12 | ### 1. Page Purpose |
| 13 | - What type of page? (homepage, landing page, pricing, feature, about) |
| 14 | - What is the ONE primary action you want visitors to take? |
| 15 | |
| 16 | ### 2. Audience |
| 17 | - Who is the ideal customer? |
| 18 | - What problem are they trying to solve? |
| 19 | - What objections or hesitations do they have? |
| 20 | - What language do they use to describe their problem? |
| 21 | |
| 22 | ### 3. Product/Offer |
| 23 | - What are you selling or offering? |
| 24 | - What makes it different from alternatives? |
| 25 | - What's the key transformation or outcome? |
| 26 | - Any proof points (numbers, testimonials, case studies)? |
| 27 | |
| 28 | ### 4. Context |
| 29 | - Where is traffic coming from? (ads, organic, email) |
| 30 | - What do visitors already know before arriving? |
| 31 | |
| 32 | --- |
| 33 | |
| 34 | ## Copywriting Principles |
| 35 | |
| 36 | ### Clarity Over Cleverness |
| 37 | If you have to choose between clear and creative, choose clear. |
| 38 | |
| 39 | ### Benefits Over Features |
| 40 | Features: What it does. Benefits: What that means for the customer. |
| 41 | |
| 42 | ### Specificity Over Vagueness |
| 43 | - Vague: "Save time on your workflow" |
| 44 | - Specific: "Cut your weekly reporting from 4 hours to 15 minutes" |
| 45 | |
| 46 | ### Customer Language Over Company Language |
| 47 | Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets. |
| 48 | |
| 49 | ### One Idea Per Section |
| 50 | Each section should advance one argument. Build a logical flow down the page. |
| 51 | |
| 52 | --- |
| 53 | |
| 54 | ## Writing Style Rules |
| 55 | |
| 56 | ### Core Principles |
| 57 | |
| 58 | 1. **Simple over complex** — "Use" not "utilize," "help" not "facilitate" |
| 59 | 2. **Specific over vague** — Avoid "streamline," "optimize," "innovative" |
| 60 | 3. **Active over passive** — "We generate reports" not "Reports are generated" |
| 61 | 4. **Confident over qualified** — Remove "almost," "very," "really" |
| 62 | 5. **Show over tell** — Describe the outcome instead of using adverbs |
| 63 | 6. **Honest over sensational** — Fabricated statistics or testimonials erode trust and create legal liability |
| 64 | |
| 65 | ### Quick Quality Check |
| 66 | |
| 67 | - Jargon that could confuse outsiders? |
| 68 | - Sentences trying to do too much? |
| 69 | - Passive voice constructions? |
| 70 | - Exclamation points? (remove them) |
| 71 | - Marketing buzzwords without substance? |
| 72 | |
| 73 | For thorough line-by-line review, use the **copy-editing** skill after your draft. |
| 74 | |
| 75 | --- |
| 76 | |
| 77 | ## Best Practices |
| 78 | |
| 79 | ### Be Direct |
| 80 | Get to the point. Don't bury the value in qualifications. |
| 81 | |
| 82 | ❌ Slack lets you share files instantly, from documents to images, directly in your conversations |
| 83 | |
| 84 | ✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires. |
| 85 | |
| 86 | ### Use Rhetorical Questions |
| 87 | Questions engage readers and make them think about their own situation. |
| 88 | - "Hate returning stuff to Amazon?" |
| 89 | - "Tired of chasing approvals?" |
| 90 | |
| 91 | ### Use Analogies When Helpful |
| 92 | Analogies make abstract concepts concrete and memorable. |
| 93 | |
| 94 | ### Pepper in Humor (When Appropriate) |
| 95 | Puns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity. |
| 96 | |
| 97 | --- |
| 98 | |
| 99 | ## Page Structure Framework |
| 100 | |
| 101 | ### Above the Fold |
| 102 | |
| 103 | **Headline** |
| 104 | - Your single most important message |
| 105 | - Communicate core value proposition |
| 106 | - Specific > generic |
| 107 | |
| 108 | **Example formulas:** |
| 109 | - "{Achieve outcome} without {pain point}" |
| 110 | - "The {category} for {audience}" |
| 111 | - "Never {unpleasant event} again" |
| 112 | - "{Question highlighting main pain point}" |
| 113 | |
| 114 | **For comprehensive headline formulas**: See [references/copy-frameworks.md](references/copy-frameworks.md) |
| 115 | |
| 116 | **For natural transition phrases**: See [references/natural-transitions.md](references/natural-transitions.md) |
| 117 | |
| 118 | **Subheadline** |
| 119 | - Expands on headline |
| 120 | - Adds specificity |
| 121 | - 1-2 sentences max |
| 122 | |
| 123 | **Primary CTA** |
| 124 | - Action-oriented button text |
| 125 | - Communicate what they get: "Start Free Trial" > "Sign Up" |
| 126 | |
| 127 | ### Core Sections |
| 128 | |
| 129 | | Section | Purpose | |
| 130 | |---------|---------| |
| 131 | | Social Proof | Build credibility (logos, stats, testimonials) | |
| 132 | | Problem/Pain | Show you understand their situation | |
| 133 | | Solution/Benefits | Connect to outcomes (3-5 key benefits) | |
| 134 | | How It Works | Reduce perceived complexity (3-4 steps) | |
| 135 | | Objection Handling | FAQ, comparisons, guarantees | |
| 136 | | Final CTA | Recap value, repeat CTA, risk reversal | |
| 137 | |
| 138 | **For detailed section types and page templates**: See [references/copy-frameworks.md](references/copy-frameworks.md) |
| 139 | |
| 140 | --- |
| 141 | |
| 142 | ## CTA Copy Guidelines |
| 143 | |
| 144 | **Weak CTAs (avoid):** |
| 145 | - Submit, Sign Up, Learn More, Click Here, Get Started |
| 146 | |
| 147 | **Strong CTAs (use):** |
| 148 | - Start Free Trial |
| 149 | - Get [Specific Thing] |
| 150 | - See [Product] in Action |
| 151 | - Create Your First [Thing] |
| 152 | - Download the Guide |
| 153 | |
| 154 | **Formula:** [Action Verb] + [What They Get] + [Qualifier if needed] |
| 155 | |
| 156 | Examples: |
| 157 | - "Start My Free Trial" |
| 158 | - "Get the Complete Checklist" |
| 159 | - "See Pricing for My Team" |
| 160 | |
| 161 | --- |
| 162 | |
| 163 | ## Page-Specific Guidance |
| 164 | |
| 165 | ### Homepage |
| 166 | - Serve multiple audiences without being generic |
| 167 | - Lead with broadest value proposition |
| 168 | - Provide clear paths for different visitor intents |
| 169 | |
| 170 | ### Landing Page |
| 171 | - Single message, single CTA |
| 172 | - Match headline to ad/traffic source |
| 173 | - Complete argument on one page |
| 174 | |
| 175 | ### Pricing Page |
| 176 | - Help visitors choose the right plan |
| 177 | - Address "which is right for me?" anxiety |
| 178 | - Make recommended plan obvious |
| 179 | |
| 180 | ### Feature Page |
| 181 | - Connect feature → benefit → outcome |
| 182 | - Show use cases and examples |
| 183 | - Clear path to try or buy |
| 184 | |
| 185 | ### About Page |
| 186 | - Tell the story of why you exist |
| 187 | - Connect mission to customer benefit |
| 188 | - Still include a CTA |
| 189 | |
| 190 | --- |
| 191 | |
| 192 | ## Voice and Tone |
| 193 | |
| 194 | Before writing, establish: |
| 195 | |
| 196 | **Formality level:** |
| 197 | - Casual/conversational |
| 198 | - Professional but friendly |
| 199 | - Formal/enterprise |
| 200 | |
| 201 | **Brand personality:** |
| 202 | - Playful or serious? |
| 203 | - Bold or understated? |
| 204 | - Technical or accessible? |
| 205 | |
| 206 | Maintain consistency, but adjust intensity: |
| 207 | - Headlines can be bolder |
| 208 | - Body copy should be clearer |
| 209 | - CTAs should be action-oriented |
| 210 | |
| 211 | --- |
| 212 | |
| 213 | ## Output Format |
| 214 | |
| 215 | When writing copy, provide: |
| 216 | |
| 217 | ### Page Copy |
| 218 | Organized by section: |
| 219 | - Headline, Subheadline, CTA |
| 220 | - Section headers and body copy |
| 221 | - Secondary CTAs |
| 222 | |
| 223 | ### Annotations |
| 224 | For key elements, explain: |
| 225 | - Why you made this choice |
| 226 | - What principle it applies |
| 227 | |
| 228 | ### Alternatives |
| 229 | For headlines and CTAs, provide 2-3 options: |
| 230 | - Option A: [copy] — [rationale] |
| 231 | - Option B: [copy] — [rationale] |
| 232 | |
| 233 | ### Meta Content (if relevant) |
| 234 | - Page title (for SEO) |
| 235 | - Meta description |
| 236 | |
| 237 | --- |
| 238 | |
| 239 | ## Related Skills |
| 240 | |
| 241 | - **copy-editing**: For polishing existing copy (use after your draft) |
| 242 | - **cro**: If page structure/strategy needs work, not just copy |
| 243 | - **emails**: For email copywriting |
| 244 | - **popups**: For popup and modal copy |
| 245 | - **ab-testing**: To test copy variations |
Related
6 picksType
- edit-articleEdit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.Jul 2026
- writing-shapeWriting, exploit — shape raw material into an article, paragraph by paragraph.Jul 2026
- writing-fragmentsWriting, explore — mine raw fragments, no structure yet.Jul 2026
- writing-beatsWriting, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.Jul 2026
- slideshowAuthor a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and…Jul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.Jul 2026
