.agents/skills/copywriting/SKILL.md
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," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
npx skillsauth add adonis0123/adonis-skills copywritingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
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):
If you have to choose between clear and creative, choose clear.
Features: What it does. Benefits: What that means for the customer.
Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.
Each section should advance one argument. Build a logical flow down the page.
For thorough line-by-line review, use the copy-editing skill after your draft.
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.
Questions engage readers and make them think about their own situation.
Analogies make abstract concepts concrete and memorable.
Puns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity.
Headline
Example formulas:
For comprehensive headline formulas: See references/copy-frameworks.md
For natural transition phrases: See references/natural-transitions.md
Subheadline
Primary CTA
| 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
Weak CTAs (avoid):
Strong CTAs (use):
Formula: [Action Verb] + [What They Get] + [Qualifier if needed]
Examples:
Before writing, establish:
Formality level:
Brand personality:
Maintain consistency, but adjust intensity:
When writing copy, provide:
Organized by section:
For key elements, explain:
For headlines and CTAs, provide 2-3 options:
development
Use this skill when the user wants to set, write, or use a goal or /goal that makes a coding agent keep working until a verifiable done condition is met. This skill configures the autonomy and stopping contract for Codex, Claude Code, or portable agent prompts; it does not perform the underlying task. Trigger on requests like 'should I set a goal?', 'set up a durable goal', 'give me a /goal prompt', 'keep refactoring until tests pass', 'I am stepping away, have the agent finish this', or goal prompts for migrations, refactors, ports, spec implementations, eval loops, backlog cleanup, or multi-checkpoint work. Do not use for single quick edits, running tests once, OKR/scrum goal questions, recurring reminders, or token-budget settings.
testing
Create safe Git feature or hotfix branches with concise names. Use this whenever the user asks to create a branch, start work on a new feature or fix, wants a `feat/...` or `hotfix/...` branch name, asks for a short branch slug from a task description, or wants help before beginning local Git work. Default to recommending the branch name and command first, then create only after user confirmation. Do not push, commit, rebase, or create PRs.
tools
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
development
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.