Copywriting
Copywriting skill from Corey Haines’ Marketing Skills collection.
Overview
Copywriting is a growth/marketing skill from Corey Haines’ Marketing Skills collection (github.com/coreyhaines31/marketingskills). Copywriting skill from Corey Haines’ Marketing Skills collection. The skill is structured around practical workflows—covering Before Writing, Copywriting Principles, Writing Style Rules, Best Practices, Page Structure Framework, CTA Copy Guidelines—so Claude can move from context gathering to concrete artifacts (briefs, copy, checklists, or audit reports) instead of generic advice. Pair it with related skills in the same collection: `copy-editing`, `cro`, `ad-creative`, `emails`.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Option A — Install just this skill (recommended)
npx skills add coreyhaines31/marketingskills --skill copywritingOption B — Install the full Marketing Skills collection
npx skills add coreyhaines31/marketingskillsThat unlocks related skills like `cro`, `copywriting`, `emails`, `ads`, and `seo-audit`.
Option C — Manual install (Claude Code)
git clone https://github.com/coreyhaines31/marketingskills.git /tmp/marketingskills
mkdir -p ~/.claude/skills
cp -R /tmp/marketingskills/skills/copywriting ~/.claude/skills/copywritingClaude.ai
Customize → Skills → Upload the `copywriting` folder as a zip / `SKILL.md` → enable the skill.
Always skim `SKILL.md` before first use so you know its triggers and related skills.
How to use it
1. **Trigger it with copywriting language** — mention the job by name or ask for the deliverable this skill owns. 2. **Share product context up front** — ICP, offer, URL, constraints, and any metrics. If `.agents/product-marketing.md` (or `.claude/product-marketing.md`) exists, the skill will read it first. 3. **Let it run the assessment** — answer clarifying questions before asking for final copy/strategy. 4. **Request a concrete artifact** — brief, audit, page outline, sequence, scorecard, or launch checklist. 5. **Close the loop** — feed performance data back so the next iteration compounds.
**Typical sections it covers:** Before Writing, Copywriting Principles, Writing Style Rules, Best Practices, Page Structure Framework, CTA Copy Guidelines, Page-Specific Guidance, Voice and Tone.
If Claude does not auto-select it, say: “Use the Copywriting skill (`copywriting`)…”.
Example prompts
- “Rewrite our homepage hero. Current headline: “The AI workspace for modern teams.” We’re a B2B project tool for agencies.”
- “Draft landing page copy for a new AI SEO feature. Sections: problem, how it works, proof, FAQ, CTA.”
- “Turn these 8 G2 quotes into headline and subhead options for the pricing page.”
- “Write 5 CTA variants for the signup page that emphasize time-to-value.”
Use cases and examples
- Rewrite a homepage hero for clarity and conversion
- Draft landing-page sections with voice-of-customer language
- Produce feature→benefit copy for a launch page
- Write CTA variants for pricing and signup surfaces
- Create onboarding empty-state microcopy
- Turn research quotes into headline angles
Prerequisites
- Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
- Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
- Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
- Permission to install third-party skills — audit SKILL.md first
- Optional: analytics or ad-platform access when the task needs real performance data
Tips
- Keep triggers specific so Copywriting fires only when that job is requested (avoids context tax).
- Load product-marketing context (ICP, voice, offer) before asking for final copy or strategy.
- Prefer one sharp deliverable per turn—brief, audit, or draft—then iterate with data.
- Audit `SKILL.md` and any scripts before production use; treat community skills as code.
- Pair with `copy-editing` and `cro` when the workflow spans channels.