Best use case
copywriting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using copywriting should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/copywriting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How copywriting Compares
| Feature / Agent | copywriting | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Copywriting
> **WHAT**: Write clear, compelling marketing copy that drives action
> **WHEN**: User wants to write, rewrite, or improve copy for homepage, landing pages, pricing pages, feature pages, about pages, or product pages
> **KEYWORDS**: write copy, improve copy, rewrite page, marketing copy, headline help, CTA copy, landing page copy, value proposition
## Reference Files
- `references/copy-frameworks.md` - Headline formulas, page templates, section types
- `references/natural-transitions.md` - Transitional phrases and signposting
## Installation
### OpenClaw / Moltbot / Clawbot
```bash
npx clawhub@latest install copywriting
```
---
## Workflow
### 1. Gather Context
Check for `.claude/product-marketing-context.md` first. If not available, ask:
**Page Purpose**
- What type of page? (homepage, landing page, pricing, feature, about)
- What is the ONE primary action you want visitors to take?
**Audience**
- Who is the ideal customer?
- What problem are they solving?
- What objections do they have?
- What language do they use to describe their problem?
**Product/Offer**
- What are you selling?
- What makes it different?
- What's the key transformation?
- Any proof points (numbers, testimonials, case studies)?
**Traffic Context**
- Where is traffic coming from? (ads, organic, email)
- What do visitors already know before arriving?
### 2. Write Copy
Structure output by section:
```
## Above the Fold
### Headline
[Primary headline - your single most important message]
### Subheadline
[Expands on headline, adds specificity, 1-2 sentences]
### Primary CTA
[Action-oriented button text]
---
## [Section Name]
[Section copy]
---
## Final CTA
[Recap value, repeat CTA, risk reversal]
```
### 3. Provide Alternatives
For headlines and CTAs, offer 2-3 options:
```
**Headline Options:**
1. "[Copy A]" — [rationale: outcome-focused]
2. "[Copy B]" — [rationale: problem-focused]
3. "[Copy C]" — [rationale: proof-focused]
```
### 4. Include Meta Content
When relevant:
- Page title (for SEO)
- Meta description
---
## Core 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
1. **Simple over complex** — "Use" not "utilize," "help" not "facilitate"
2. **Specific over vague** — Avoid "streamline," "optimize," "innovative"
3. **Active over passive** — "We generate reports" not "Reports are generated"
4. **Confident over qualified** — Remove "almost," "very," "really"
5. **Show over tell** — Describe the outcome instead of using adverbs
6. **Honest over sensational** — Never fabricate statistics or testimonials
---
## Headline Formulas (Quick Reference)
**Outcome-Focused:**
- "{Achieve outcome} without {pain point}"
- "Turn {input} into {outcome}"
- "[Outcome] in [timeframe]"
**Problem-Focused:**
- "Never {unpleasant event} again"
- "{Question highlighting pain point}?"
- "Stop [pain]. Start [pleasure]."
**Audience-Focused:**
- "{Product type} for {audience}"
- "You don't have to {skill} to {outcome}"
**Proof-Focused:**
- "[Number] [people] use [product] to [outcome]"
See `references/copy-frameworks.md` for complete formulas and page templates.
---
## CTA 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]
---
## Page-Specific Guidance
| Page Type | Key Focus |
|-----------|-----------|
| Homepage | Serve multiple audiences without being generic; clear paths for different intents |
| Landing Page | Single message, single CTA; match headline to traffic source |
| Pricing Page | Help visitors choose the right plan; address "which is right for me?" |
| Feature Page | Connect feature → benefit → outcome; show use cases |
| About Page | Tell why you exist; connect mission to customer benefit |
---
## Quality Checklist
Before finalizing, check for:
- [ ] Jargon that could confuse outsiders?
- [ ] Sentences trying to do too much?
- [ ] Passive voice constructions?
- [ ] Exclamation points? (remove them)
- [ ] Marketing buzzwords without substance?
- [ ] Generic claims with no proof?
---
## NEVER
- Use exclamation points in headlines or body copy
- Write vague claims like "best-in-class" or "industry-leading"
- Fabricate statistics or testimonials
- Bury the value proposition below the fold
- Use jargon the customer wouldn't use
- Write passive voice when active is clearer
- Submit copy without providing alternatives for key elements
---
## Related Skills
- `page-cro` - Page structure and conversion optimization
- `marketing-psychology` - Apply psychological principles to copy
- `marketing-ideas` - Tactical marketing approachesRelated Skills
schema-markup
Add, fix, or optimize schema markup and structured data. Use when the user mentions schema markup, structured data, JSON-LD, rich snippets, schema.org, FAQ schema, product schema, review schema, or breadcrumb schema.
prompt-engineering
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, designing production prompt templates, or building AI-powered features.
professional-communication
Write effective professional messages for software teams. Use when drafting emails, Slack/Teams messages, meeting agendas, status updates, or translating technical concepts for non-technical audiences. Triggers on email, slack, teams, message, meeting agenda, status update, stakeholder communication, escalation, jargon translation.
persona-docs
Create persona documentation for a product or codebase. Use when asked to create persona docs, document target users, define user journeys, document onboarding flows, or when starting a new product and needing to define its audience. Persona docs should be the first documentation created for any product.
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
game-changing-features
Find 10x product opportunities and high-leverage improvements. Use when the user wants strategic product thinking, mentions 10x, wants to find high-impact features, or asks what would make a product dramatically more valuable.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
brainstorming
Explore ideas before implementation through collaborative dialogue. Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Turns ideas into fully formed designs and specs through structured conversation.
Article Illustrator
When the user wants to add illustrations to an article or blog post. Triggers on: "illustrate article", "add images to article", "generate illustrations", "article images", or requests to visually enhance written content. Analyzes article structure, identifies positions for visual aids, and generates illustrations using a Type x Style two-dimension approach.
subagent-driven-development
Execute implementation plans by dispatching a fresh subagent per task with two-stage review (spec compliance then code quality). Use when you have an implementation plan with mostly independent tasks and want high-quality, fast iteration within a single session.
skill-judge
Evaluate Agent Skill quality against official specifications. Use when reviewing SKILL.md files, auditing skill packages, improving skill design, or checking if a skill follows best practices. Provides 8-dimension scoring (120 points) with actionable improvements. Triggers on review skill, evaluate skill, audit skill, improve skill, skill quality, SKILL.md review.
skill-creator
WHAT: Guide for creating effective AI agent skills - modular packages that extend Claude's capabilities with specialized knowledge, workflows, and tools. WHEN: User wants to create, write, author, or update a skill. User asks about skill structure, SKILL.md format, or how to package domain knowledge for AI agents. KEYWORDS: "create a skill", "make a skill", "new skill", "skill template", "SKILL.md", "agent skill", "write a skill", "skill structure", "package a skill"