copywriting
Skill3 starsChanged 31 days agoMITView on GitHub
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," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.
191 other projects use a version of this, 133 of them edited.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillsedited, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillsedited, first seen Nov 8, 2026
- insight68/Skillsedited, first seen Nov 8, 2026
- figueroaignacio/ignaciofigueroa.devedited, first seen Nov 8, 2026
Used with
Projects with it also use paywalls, popups and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CesarjoquinSkillpaywalls
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
Also in 17 projects that use this
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 16 projects that use this
ukunal91appSkillrevops
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
Also in 38 projects that use this
roerohanSkillemails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 21 projects that use this
timruebenachSkillcompetitor-profiling
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.
Also in 25 projects that use this
silvainfmSkillcompetitor-alternatives
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
Also in 33 projects that use this
- +4 more from Cesarjoquin
Other versions191 projects use a version of this.
Word for word · 4
- anis-dr/skills★ 3100% same
- danielvieirasilva0257-droid/claude-skills★ 1100% same
- DoodleX/Claude-Code★ 1100% same
- masterpeteworld/claude-skills★ 0100% same
Edited · 133
- coreyhaines31/marketingskills★ 59k64% same
- TheCraigHewitt/seomachine★ 7.5k87% same
- stagewise-io/stagewise★ 6.8k93% same
- legions-developer/evilcharts★ 3.2k93% same
- compozy/compozy★ 2.9k86% same
- databuddy-analytics/Databuddy★ 1.2k87% same
- KartikLabhshetwar/screenshot-studio★ 1.1k87% same
- KartikLabhshetwar/stage★ 1.1k87% same
- LeoYeAI/openclaw-marketing-skills★ 1k89% same
- Nexus-JPF/note-companion★ 87493% same
123 more not listed
Wrote their own version · 54
- supabase/supabase★ 115ksame name
- ZJU-REAL/Easel★ 4.5ksame name
- kostja94/marketing-skills★ 1.1ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- LOGIN-TB/claude-skills★ 82same name
- okou-ai/okou-skills★ 81same name
- vm0-ai/vm0-skills★ 81same name
- nahid-sparktales/agent-dispatcher★ 59same name
- Rylaispirit/rylai-codex-hermes-skills★ 56same name
- Infinite-Labs-AI/infinite-skills★ 43same name
44 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- api-and-interface-designSkill
- apple-designSkill
- codebase-designSkill
- code-reviewSkill
- code-simplificationSkill
- constraint-driven-developmentSkill
- content-strategySkill
- copy-editingSkill
- diagnosing-bugsSkill
- documentation-and-adrsSkill
- find-skillsSkill
- frontend-designSkill
- github-workflowSkill
- git-workflow-and-versioningSkill
- impeccableSkill
- marketing-ideasSkill
- marketing-psychologySkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- playwright-best-practicesSkill
- product-marketingSkill
- security-and-hardeningSkill
- socialSkill
- supabase-postgres-best-practicesSkill
- tddSkill
- vercel-react-best-practicesSkill
- vibecoding-deliverySkill
The file
We split this skill into the rules it gives an agent
9 rules. 4 are common, 4 are distinctive, and 1 is very specific to this project.
4
Common
Most of the 175 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …
- Distinctive: line 44
If you have to choose between clear and creative, choose clear.
- Common: line 56
Use words your customers use.
- Distinctive: line 68
Specific over vague: Avoid "streamline," "optimize," "innovative"
- Distinctive: line 70
Confident over qualified: Remove "almost," "very," "really"
- Distinctive: line 108
Before handing over any draft, run the self-check in references/ai-tells.md: search for the banned patterns, read every sentence over 20 …
- Common: line 192
Create Your First [Thing]
- Common: line 256
When writing copy, provide:
- Common: line 283
cro: If page structure/strategy needs work, not just copy
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), 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. Clarity also converts. Clearer positioning and copy is associated with +81% conversions, a 38% shorter sales cycle, 28% lower CAC, and 175% more referrals. When a reader has to decode your line, you've lost them.
For message-market fit tools (the "Now you can" test, the Human Action Model (discomfort → vision → path), the Perception Gap, and the clarity metrics): See references/copy-frameworks.md
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: Fabricated statistics or testimonials erode trust and create legal liability
Quick Quality Check
- Any AI tells? (see No AI Tells below)
- 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.
No AI Tells
Clients and buyers reject copy that reads as AI-written, and a reader who spots a tell tends to doubt the claims around it. Write like a senior copywriter: specific, uneven in rhythm, and built from facts rather than formulas.
Never write these
- Contrast reveals. "It's not X, it's Y." "Not because X. Because Y." "Not just X, but Y." State Y directly, with the reason.
- Negation lists. "No setup call, no templates, no waiting on IT. No contract." Say what does happen. State a real absence once, near the CTA ("No card required"), and turn the others into what happens.
- Trailing pile-ons. A full claim followed by a comma and more clauses: "...the data you already have, no exports, no spreadsheets, no second copy." End the sentence at the claim.
- Self-answered questions and colon reveals. "The result? 3x faster." "The best part: it learns." Just say it. FAQ questions and a reader's own question ("Need to share a screenshot?") are fine.
- Stock openers and phrases. "In today's fast-paced world," "Whether you're X or Y," "Here's the thing," "Say goodbye to," "X, reimagined," "Unlock the power of," "Take it to the next level."
- Em dashes in short copy. Headlines, subheads, ads, social posts, and subject lines use none.
Keep these rare
- At most one fragment and one list of three per section (a hero, a page section, or one short post). CTA microcopy and a real three-feature list are fine.
- Words like seamless, robust, powerful, unlock, and streamline: replace them with the fact they stand in for.
- Swap test: if a line would work unchanged on a competitor's site, rewrite it. If you lack the differentiator to fix it, flag
[NEED: differentiator].
Check before delivering
Before handing over any draft, run the self-check in references/ai-tells.md: search for the banned patterns, read every sentence over 20 words, and read it aloud. Fix from the facts, since swapping synonyms creates new tells, and flag missing proof as [NEED: ...] rather than inventing it.
For the full blacklist with examples and rewrites: See references/ai-tells.md
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
A question that names the reader's pain can open a section well.
- "Hate returning stuff to Amazon?"
- "Tired of chasing approvals?"
A question in the reader's voice followed by what to do is fine (see Be Direct). A question that labels your own claim ("The result? 3x faster.") is an AI tell.
Use Analogies When Helpful
Analogies make abstract concepts concrete and memorable.
Pepper in Humor (When Appropriate)
Puns and wit make copy memorable when they fit the brand and don't cost 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
Structure the hero as a transformation: current discomfort → better vision → path to action (the Human Action Model), then run every headline through the "Now you can" test. 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: [why]
- Option B: [copy]. Rationale: [why]
Meta Content (if relevant)
- Page title (for SEO)
- Meta description
Related Skills
- copy-editing: For polishing existing copy (use after your draft)
- cro: If page structure/strategy needs work, not just copy
- emails: For email copywriting
- popups: For popup and modal copy
- ab-testing: To test copy variations
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

