writing-copy — Claude Code skill: marketing and UI copy
A skill that gives the agent rules for marketing copy: headlines, CTAs, emails, interface microcopy. Useful when landing pages and UI text live in the same repo.
npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a claude-codeWhat writing-copy does
The skill lays out principles the agent follows when writing text: clarity over cleverness, benefits over features, one idea per section, active voice, short sentences. Then it walks through page sections — hero, features, social proof, a repeated CTA. Each part comes with a length target: an 8-12 word headline, a 15-25 word subheadline.
Separate sections cover buttons and microcopy. The agent avoids "Submit" or "Click here" and writes error and empty-state messages that say what happened and what to do next. There is an email block too: a 6-10 word subject line, one CTA in the body, a P.S. for urgency.
Install runs through npx skills add with a platform flag, and the skill file lands at ~/.claude/skills/writing-copy/SKILL.md. The guidance and examples are written for English-language products, so tone advice is tuned to English — for another language you set the wording yourself.
What it helps with
- draft a hero headline and subheadline for a landing page
- replace a "Submit" button label with something specific
- rewrite an error message so the user knows the next step
- write an onboarding email with a single call to action
- fill an empty state with a hint instead of "No data"
Example prompts for the agent
- write the hero section copy for our landing page
- rewrite the error messages in the checkout form
- draft an onboarding email with one CTA
How to install writing-copy
1Skills CLI (Vercel)
npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a claude-code2Manually: put the files in place
~/.claude/skills/writing-copy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/writing-copy/
1Skills CLI (Vercel)
npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a codex2Manually: put the files in place
.agents/skills/writing-copy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a cursor2Manually: put the files in place
.cursor/skills/writing-copy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install spencerpauly/awesome-cursor-skills writing-copy2Manually: put the files in place
.github/skills/writing-copy/SKILL.md1Skills CLI (Vercel)
npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a gemini-cli2Platform CLI
gemini skills install https://github.com/spencerpauly/awesome-cursor-skills --path resources/writing-copyManually: put the files in place
.devin/skills/writing-copy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about writing-copy
How do I install writing-copy in Claude?
Run npx skills add spencerpauly/awesome-cursor-skills --skill writing-copy -a claude-code. The skill file ends up at ~/.claude/skills/writing-copy/SKILL.md.
What does writing-copy do?
It hands the agent a set of rules for marketing text: headlines, CTAs, interface microcopy, emails. The agent leans on them whenever it writes or edits copy in your project.
Which platforms does the skill support?
Besides Claude there are commands for Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. For GitHub Copilot the install is gh skill install spencerpauly/awesome-cursor-skills writing-copy.
Source text
SKILL.md · CC0-1.0
---
name: writing-copy
description: Write marketing copy for landing pages, product descriptions, CTAs, emails, and app UI text.
user-invocable: true
---
# Writing Copy
Write clear, compelling copy for products and marketing.
## Principles
1. **Clarity over cleverness** — users should instantly understand what you're saying
2. **Benefits over features** — "Save 2 hours a day" beats "AI-powered automation"
3. **One idea per section** — don't overload the reader
4. **Active voice** — "We send your report" not "Your report will be sent"
5. **Short sentences** — aim for 15-20 words per sentence
## Landing Page Structure
### Hero Section
- **Headline**: One sentence, states the core value (8-12 words)
- **Subheadline**: Expands on the headline, addresses who it's for (15-25 words)
- **CTA**: Clear action verb ("Start free trial", "Get started", "Try for free")
```
Headline: Ship faster with AI-powered code review
Subheadline: Catch bugs, enforce standards, and merge with confidence —
built for teams that move fast.
CTA: Start free trial →
```
### Features Section
For each feature:
- **Short title** (3-5 words)
- **One sentence** explaining the benefit
- Optional: icon or screenshot
### Social Proof
- Customer logos, testimonials, metrics
- Specific numbers: "Used by 10,000+ teams" not "Used by many teams"
- Quotes with name, title, company
### CTA Section
- Repeat the primary CTA
- Address objections: "No credit card required", "Free for up to 5 users"
## Button & CTA Copy
Good:
- "Start free trial"
- "Get started — it's free"
- "Download the app"
- "See pricing"
- "Book a demo"
Bad:
- "Submit"
- "Click here"
- "Learn more" (too vague as a primary CTA)
- "Get started now for free today!" (too long)
## Microcopy (UI Text)
**Error messages:**
- Say what happened and what to do: "Payment failed. Please check your card details and try again."
- Not: "Error 422" or "Something went wrong"
**Empty states:**
- Guide the user: "No projects yet. Create your first project to get started."
- Not: "No data"
**Confirmation dialogs:**
- Be specific: "Delete this project? This will remove all tasks and cannot be undone."
- Button: "Delete project" (not "OK")
**Loading states:**
- "Setting up your workspace..." (not "Loading...")
## Email Copy
- **Subject line**: 6-10 words, specific, no ALL CAPS
- **First line**: Get to the point — why should they care?
- **Body**: One CTA, not three
- **P.S.**: Use for urgency or a secondary point (highest-read part after the subject)
## Tips
- Read your copy out loud — if it sounds awkward, rewrite it
- Cut every word that isn't doing work
- Use the "so what?" test: after every sentence, ask "so what?" — the answer should be obvious
- A/B test headlines and CTAs when possible
- Match the tone to your audience (developer docs ≠ consumer marketing)
© spencerpauly · CC0-1.0 · spencerpauly/awesome-cursor-skills
