skills / coreyhaines31 / marketingskills / copywriting
Copywriting
A high-intent writing skill focused on conversion-oriented page copy with clear structure, audience fit, and stronger CTA performance.
Source description: 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...
npx skills add https://github.com/coreyhaines31/marketingskills --skill copywritingOn this page
Our added value (verification layer)
This page is not only a source mirror. We add reproducibility, risk controls, and operations guidance on top of the original skill definition.
- Execution/Security/Maintainability scoring with explicit criteria
- Compatibility matrix across runtime environments
- Verification log with check commands and observed outcomes
- Common failure fixes and rollback triggers for production safety
Overall score
90/100
Execution
90
Security
92
Maintainability
88
Quick install (universal)
Primary command for most environments:
npx skills add https://github.com/coreyhaines31/marketingskills --skill copywritingManual fallback (if your runtime does not support direct installer command):
npx skills add https://github.com/coreyhaines31/marketingskills --skill copywritingRestart your current agent/runtime to reload installed skills.Run a low-risk dry run: "rewrite this feature section for higher conversion clarity".
- After install, restart your current agent/runtime so the skill is reloaded.
- Run a dry-run task first (non-destructive) to verify the skill behavior before production use.
SKILL.md (rendered source content)
Readable source reference for this skill. Added verification notes are shown in the sections below.
Copywriting
You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
Before Writing
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Page Purpose
- What type of page? (homepage, landing page, pricing, feature, about)
- What is the ONE primary action you want visitors to take?
2. Audience
- Who is the ideal customer?
- What problem are they trying to solve?
- What objections or hesitations do they have?
- What language do they use to describe their problem?
3. Product/Offer
- What are you selling or offering?
- What makes it different from alternatives?
- What's the key transformation or outcome?
- Any proof points (numbers, testimonials, case studies)?
4. Context
- Where is traffic coming from? (ads, organic, email)
- What do visitors already know before arriving?
Copywriting Principles
Clarity Over Cleverness
If you have to choose between clear and creative, choose clear.
Benefits Over Features
Features: What it does. Benefits: What that means for the customer.
Specificity Over Vagueness
- Vague: "Save time on your workflow"
- Specific: "Cut your weekly reporting from 4 hours to 15 minutes"
Customer Language Over Company Language
Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.
One Idea Per Section
Each section should advance one argument. Build a logical flow down the page.
Writing Style Rules
Core Principles
- Simple over complex — "Use" not "utilize," "help" not "facilitate"
- Specific over vague — Avoid "streamline," "optimize," "innovative"
- Active over passive — "We generate reports" not "Reports are generated"
- Confident over qualified — Remove "almost," "very," "really"
- Show over tell — Describe the outcome instead of using adverbs
- Honest over sensational — Never fabricate statistics or testimonials
Quick Quality Check
- Jargon that could confuse outsiders?
- Sentences trying to do too much?
- Passive voice constructions?
- Exclamation points? (remove them)
- Marketing buzzwords without substance?
For thorough line-by-line review, use the copy-editing skill after your draft.
Best Practices
Be Direct
Get to the point. Don't bury the value in qualifications.
❌ Slack lets you share files instantly, from documents to images, directly in your conversations
✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.
Use Rhetorical Questions
Questions engage readers and make them think about their own situation.
- "Hate returning stuff to Amazon?"
- "Tired of chasing approvals?"
Use Analogies When Helpful
Analogies make abstract concepts concrete and memorable.
Pepper in Humor (When Appropriate)
Puns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity.
Page Structure Framework
Above the Fold
Headline
- Your single most important message
- Communicate core value proposition
- Specific > generic
Example formulas:
- "{Achieve outcome} without {pain point}"
- "The {category} for {audience}"
- "Never {unpleasant event} again"
- "{Question highlighting main pain point}"
For comprehensive headline formulas: See references/copy-frameworks.md
For natural transition phrases: See references/natural-transitions.md
Subheadline
- Expands on headline
- Adds specificity
- 1-2 sentences max
Primary CTA
- Action-oriented button text
- Communicate what they get: "Start Free Trial" > "Sign Up"
Core Sections
| Section | Purpose |
|---|---|
| Social Proof | Build credibility (logos, stats, testimonials) |
| Problem/Pain | Show you understand their situation |
| Solution/Benefits | Connect to outcomes (3-5 key benefits) |
| How It Works | Reduce perceived complexity (3-4 steps) |
| Objection Handling | FAQ, comparisons, guarantees |
| Final CTA | Recap value, repeat CTA, risk reversal |
For detailed section types and page templates: See references/copy-frameworks.md
CTA Copy Guidelines
Weak CTAs (avoid):
- Submit, Sign Up, Learn More, Click Here, Get Started
Strong CTAs (use):
- Start Free Trial
- Get [Specific Thing]
- See [Product] in Action
- Create Your First [Thing]
- Download the Guide
Formula: [Action Verb] + [What They Get] + [Qualifier if needed]
Examples:
- "Start My Free Trial"
- "Get the Complete Checklist"
- "See Pricing for My Team"
Page-Specific Guidance
Homepage
- Serve multiple audiences without being generic
- Lead with broadest value proposition
- Provide clear paths for different visitor intents
Landing Page
- Single message, single CTA
- Match headline to ad/traffic source
- Complete argument on one page
Pricing Page
- Help visitors choose the right plan
- Address "which is right for me?" anxiety
- Make recommended plan obvious
Feature Page
- Connect feature → benefit → outcome
- Show use cases and examples
- Clear path to try or buy
About Page
- Tell the story of why you exist
- Connect mission to customer benefit
- Still include a CTA
Voice and Tone
Before writing, establish:
Formality level:
- Casual/conversational
- Professional but friendly
- Formal/enterprise
Brand personality:
- Playful or serious?
- Bold or understated?
- Technical or accessible?
Maintain consistency, but adjust intensity:
- Headlines can be bolder
- Body copy should be clearer
- CTAs should be action-oriented
Output Format
When writing copy, provide:
Page Copy
Organized by section:
- Headline, Subheadline, CTA
- Section headers and body copy
- Secondary CTAs
Annotations
For key elements, explain:
- Why you made this choice
- What principle it applies
Alternatives
For headlines and CTAs, provide 2-3 options:
- Option A: [copy] — [rationale]
- Option B: [copy] — [rationale]
Meta Content (if relevant)
- Page title (for SEO)
- Meta description
Related Skills
- copy-editing: For polishing existing copy (use after your draft)
- page-cro: If page structure/strategy needs work, not just copy
- email-sequence: For email copywriting
- popup-cro: For popup and modal copy
- ab-test-setup: To test copy variations
Required permissions
file
Compatibility matrix
| Environment | Status | Notes |
|---|---|---|
| Local macOS workspace | pass | Loads and runs as prompt-driven writing workflow. |
| Server runtime (restricted policy) | pass | No destructive commands; mostly text generation and editing. |
| No-file runtime | partial | Works, but cannot read local marketing context files. |
Verification log
Repository reachable
git ls-remote https://github.com/coreyhaines31/marketingskills
result: pass
Skill structure present
test -f ~/.claude/skills/copywriting/SKILL.md
result: pass
Dry-run copy task
run prompt: "rewrite homepage hero for B2B startup founders"
result: pass
Security notes
- Low operational risk: text-generation workflow with no destructive actions.
- Review claims in generated copy before publishing.
- Do not include private customer data in prompts.
Common failures and fixes
Output is generic and not persuasive
Provide audience pains, objections, and proof points before drafting.
CTA feels weak
Switch to action + outcome format and provide 3 variants.
Copy sounds too technical
Ask the skill to rewrite in customer language with simpler terms.
Quick FAQ
How do I install this skill quickly?
Run npx skills add https://github.com/coreyhaines31/marketingskills --skill copywriting, then restart your runtime to reload skills.
What should I check before production rollout?
Confirm permissions, run a non-destructive dry run, and review rollback triggers.
What if install succeeds but actions do not run?
Verify SKILL.md location, restart runtime, and check environment/dependency readiness.
Recent changes
- 2026-02-13: Synced full source SKILL.md and source description from canonical file.
- 2026-02-13: Added FAQ schema and in-page navigation anchors.
- 2026-02-13: Added copywriting-first tutorial cross-links.
Rollback triggers
- Generated copy introduces unverifiable claims.
- Conversion metrics drop after replacing existing page copy.
- Brand/legal review flags unsupported statements.
Known issues
Insufficient context leads to bland copy
Use a short intake template before generation.
Overly long sections
Enforce one idea per section and set max paragraph length.
Related tutorials
Site references
- Source repository
- Original path: /coreyhaines31/marketingskills/copywriting
- License: check source repository
- Fetched/verified: 2026-02-13
- Third-party source summary with added verification and security notes.
- Alternative: webapp-testing
- Alternative: ai-sdk