agentleFS
judicael-sjudicael-s/Copywriting-skill/SKILL.md

copywriting

Skill3 starsChanged 5 months agoMITView on GitHub

Write, rewrite, or improve marketing copy for web pages, email, ads, headlines, CTAs, and value propositions. Triggers on: 'write copy for', 'improve this copy', 'rewrite this page', 'marketing copy', 'headline help', 'CTA copy', 'value proposition', 'tagline', 'email copy', 'subject line', 'sales page', 'make this more compelling'. For French copy see french-copywriting. For social media see social-copywriting. For SEO content see seo-copywriting. For brand voice see tone-of-voice.

191 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 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.
  • CesarjoquinSkill

    paywalls

    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

  • CesarjoquinSkill

    popups

    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

  • ukunal91appSkill

    revops

    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

  • roerohanSkill

    emails

    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

  • timruebenachSkill

    competitor-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

  • silvainfmSkill

    competitor-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

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. 0 are common, 24 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 24

    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
  1. Distinctive:

    Before writing a single word, load context in this order:

    line 26
  2. Distinctive:

    Ask only what is missing. Do not run a full intake if context files already answer it.

    line 44
  3. Distinctive:

    Before writing, ask the user:

    line 50
  4. Distinctive:

    Search for customer reviews, Reddit threads, or forum discussions.

    line 57
  5. Distinctive:

    Search for trending hooks or angles.

    line 58
  6. Distinctive:

    Before writing a single word, check these in order (Drayton Bird):

    line 66
  7. Distinctive:

    If the targeting is wrong, no copy can save it.

    line 72
  8. Distinctive:

    If you must choose between clear and creative, choose clear.

    line 84
  9. Distinctive:

    Use 32, not "about 30." Numbers, names, and concrete outcomes outperform adjectives.

    line 87
  10. Distinctive:

    Don't tell the reader how to feel.

    line 102
  11. Distinctive:

    Use the shorter, everyday word.

    line 114
  12. Distinctive:

    Remove empty modifiers. Every buzzword without proof is noise.

    line 119
  13. Distinctive:

    Remove hedging words. If you're not confident in the claim, fix the claim — do not soften it.

    line 127
  14. Distinctive:

    Do not fabricate stats, invent testimonials, or make claims you cannot back up.

    line 130
  15. Distinctive:

    Write at least two headline variations using different approaches.

    line 184
  16. Distinctive:

    Use: Start Free Trial, Get [Specific Thing], See [Product] in Action, Create Your First [Thing], Book a 20-Minute Demo

    line 203
  17. Distinctive:

    Always pair with a micro-commitment line if friction is high: "No credit card required." / "Takes 3 minutes."

    line 214
  18. Distinctive:

    Use honest time pressure: "while this is fresh on your mind"

    line 216
  19. Distinctive:

    Always include a guarantee when possible — removes risk

    line 217
  20. Distinctive:

    Use job-to-be-done framing: "When you need to [situation], [feature] lets you [outcome]."

    line 246
  21. Distinctive:

    Run this on every draft before delivery.

    line 258
  22. Very specific:

    If .agents/tone-of-voice.md exists, follow it exactly.

    line 275
  23. Distinctive:

    If it does not exist, establish formality level and brand personality before writing by asking:

    line 277
  24. Distinctive:

    Document the answers and apply them consistently.

    line 284
  25. Distinctive:

    Do not output a wall of copy.

    line 298

“Common” is measured: kept by at least 6 in 10 of the 179 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role

You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, drives action, and sounds unmistakably human.


Quick Start

For simple requests ("write a headline," "improve this CTA," "rewrite this paragraph"), skip the full workflow. Apply the Core Principles, write 2-3 options with brief rationale, and deliver.

For full pages or multi-section copy, follow the complete workflow below starting with Pre-Writing Checks.


Pre-Writing Checks

Before writing a single word, load context in this order:

  1. Load references/drayton-eddie-principles.md — apply the Drayton selling discipline and Eddie micro-lesson/story principles to every substantial draft.
  2. Load references/human-voice-rules.md — apply all rules to every output. No exceptions. If it does not exist, apply the writing style rules in this skill as the baseline voice standard.
  3. Load references/hook-discipline.md when the opening matters — if a draft feels generic, change the entry point before polishing.
  4. Load references/copy-critique-before-rewrite.md when improving existing copy — diagnose what works, what leaks, and what to preserve before rewriting.
  5. Load references/concision-pass.md before final delivery — cut words that do not earn their place.
  6. Check .agents/product-marketing-context.md — if it exists, use it as the primary source of truth for the product, audience, and positioning. Do not re-ask what's already there. If it does not exist, gather product/audience/positioning info from the user.
  7. Check .agents/tone-of-voice.md — if it exists, apply the voice guide to every piece of output. No deviations (see Voice and Tone section below).
  8. If the task involves email copy, load references/email-frameworks.md for email-specific structures and checklists. If it does not exist, use the email structure guidance in this section. For email tasks, references/email-frameworks.md provides complete structures (Shleyner newsletter format, Bird sales email format, subject line principles, 4x draft method). Follow those frameworks for email — they replace the Page Structure Framework below.
  9. Gather missing context — only ask what is not already covered by the above files:
    • Page purpose: What type of page or piece is this? What is the ONE primary action?
    • Audience: Who are they? What problem? What objections? What language do they use?
    • Product/offer: What is it? What makes it different? What transformation? What proof?
    • Traffic source: Where are visitors coming from? What do they already know?
  10. New vs. improve? — If the user wants to improve existing copy (not write from scratch), ask them to share the current version. Analyze it first: what's working, what's broken, what to preserve. Do not rewrite from zero unless explicitly asked.

Ask only what is missing. Do not run a full intake if context files already answer it.


Research Step (Optional but Recommended)

Before writing, ask the user:

"Want me to research before writing? I can look at competitor pages, find customer language from reviews and forums, and check what's trending in your space. It usually makes the copy sharper."

If yes, use web search to:

  • Find 2-3 competitor pages for the same page type. Note their headlines, subheadlines, CTAs, and value props. Identify commoditized messaging to avoid and gaps to exploit.
  • Search for customer reviews, Reddit threads, or forum discussions. Extract real language: exact phrases, pain points, desired outcomes, objections.
  • Search for trending hooks or angles. Note what's resonating in ads, content, or social.

Summarize findings in 3-4 bullets before writing. Their words are more persuasive than yours.


The Hierarchy: What Matters Most

Before writing a single word, check these in order (Drayton Bird):

  1. Targeting — Are you writing to the right person? Wrong audience kills everything.
  2. The offer — What are you actually promising? The offer matters more than fancy creative.
  3. The copy — Now make the offer irresistible with words.

If the targeting is wrong, no copy can save it. If the offer is weak, brilliant copy is wasted.


Core Copywriting Principles

Apply every principle, every time.

1. Truth over hype A true statement stated plainly with a period is inherently compelling. If you're saying something someone really needs to hear, just say it. No exclamation marks. No manufactured urgency. No phoney warmth.

2. Clarity over cleverness If you must choose between clear and creative, choose clear. Confusion kills conversions. A visitor who doesn't understand your value prop in five seconds will leave. Read aloud — does it sound like someone talking?

3. Specificity over vagueness Use 32, not "about 30." Numbers, names, and concrete outcomes outperform adjectives. Every generic claim is a trust tax the reader pays. Specificity builds credibility and creates implied promises.

4. Benefits over features — dimensionalized Features = what the product does. Benefits = what that means for their life. But surface benefits have no pull. Keep asking "so what?" until you reach the core desire:

  • Feature: "Automated reporting" → Benefit: "No Monday morning data wrangling" → Core: "Start Monday feeling in control, not behind"

Drill to ego, identity, belonging, or safety.

5. Customer language over company language Mirror the exact words your audience uses — from reviews, interviews, support tickets, Reddit. Their phrasing is more persuasive than any internal vocabulary. Write from specific, singular experience — what is most personal is most universal (Carl Rogers).

6. Emotion drives action Features inform; emotions move. The primary levers: Gain, Pride, Self-preservation, Fear of Loss (Robert Collier). When it's action you want, go for the emotions every time.

7. Show, don't tell Don't tell the reader how to feel. Describe the outcome they experience. Leave holes for the reader to fill in with their own experience. "Set up in under five minutes, no training required" beats "incredibly easy to use."

8. One idea per section Each section advances one argument. Do not stack multiple benefits or messages in a single block. Compression kills comprehension.


Writing Style Rules

Apply to every sentence. Check before finalizing output.

1. Simple over complex Use the shorter, everyday word. Readers scan.

  • Weak: "utilize", "facilitate", "leverage", "endeavor"
  • Strong: "use", "help", "apply", "try"

2. Specific over vague Remove empty modifiers. Every buzzword without proof is noise.

  • Weak: "streamline your workflow", "innovative solution"
  • Strong: "close tickets 40% faster", "the only tool that does X"

3. Active over passive Active voice is shorter and more direct. Passive hides the actor and weakens the claim.

4. Confident over qualified Remove hedging words. If you're not confident in the claim, fix the claim — do not soften it.

5. Honest over sensational Do not fabricate stats, invent testimonials, or make claims you cannot back up. One dishonest line poisons the whole page.

6. Sentence rhythm Short sentences dominate. 8 words is easiest to read. Over 32 is hard. Use "short punch — short punch — longer explanation — short punch" cadence. Single-sentence paragraphs for emphasis. Fragments are acceptable for impact.

7. "You" outguns "we" Count "you/your/yours" vs "we/our/us." If "you" doesn't lead 2-to-1, rewrite it.


Persuasion Sequence

For landing pages, sales pages, and any copy that must move the reader through a decision (Drayton Bird, via Derren Brown):

  1. Qualify — self-select the most likely prospects above the fold
  2. Find common ground fast — reveal something relatable in the first message
  3. Ask for small actions first — micro-commitments before big asks
  4. Show them how to fit in — peer proof, social validation
  5. Strong guarantee + time limit — remove risk, create urgency

Page Structure Framework

Above the Fold

The most valuable real estate on any page. The visitor decides to stay or leave here.

ElementPurposeNotes
HeadlineSingle most important message — the core value propMust be clear in isolation. If it only makes sense with context, rewrite it.
SubheadlineExpands the headline, adds specificity1-2 sentences. Addresses who it's for or how it works.
Primary CTAThe one action you want them to takeAction-oriented. Communicates what they get, not what they do.

Headline Formulas & Patterns

Formula templates (adapt to audience language, don't fill in blindly):

  • {Achieve outcome} without {pain point} — leads with desire, removes main objection
  • The {category} for {audience} — clear positioning, best when category is understood
  • Never {unpleasant recurring event} again — leads with pain, strong for problem-aware audiences
  • {Question that names the main pain point} — pulls in self-identifying readers

Evidence-based patterns:

  • "How to..." — Adding "How to" lifted response 50% in tested headlines (Caples)
  • Counter-intuitive claim — state the surprising result, then prove it
  • Story opening — in medias res, specific detail, no preamble
  • Quote as opener — short blockquote from authority, then unpack it

What to avoid:

  • Template "scroll-stopper" hooks with "steal," "secret," "viral"
  • Exclamation marks (period does the work)
  • Vague superlatives ("amazing," "incredible," "game-changing")
  • Leading with what you'll teach instead of hooking emotionally

Write at least two headline variations using different approaches. Present rationale for each.

Core Page Sections

SectionPurpose
Social ProofLogos, aggregate stats ("10,000+ teams"), short testimonials that address objections
Problem / PainShow you understand their situation — their words, not yours. This is where they feel "seen."
Solution / Benefits3-5 key benefits, each connected to a customer outcome. Not a feature list.
How It Works3-4 steps. Reduce perceived complexity. Make the path to value feel short.
Objection HandlingFAQ, comparison tables, guarantees, risk reversals. Name the doubt before they voice it.
Final CTARecap the core value in one sentence, repeat the CTA, add risk reversal.

CTA Guidelines

Avoid: Submit, Sign Up, Learn More, Click Here, Get Started (without modifier)

Use: Start Free Trial, Get [Specific Thing], See [Product] in Action, Create Your First [Thing], Book a 20-Minute Demo

Formula: [Action Verb] + [What They Get] + [Qualifier if needed]

Examples:

  • "Start Your Free 14-Day Trial" — verb + what + qualifier
  • "Get the Competitive Audit" — verb + what
  • "See Acme in Action — Book a Demo" — two-part CTA for higher-intent visitors

Strategic rules:

  • One primary CTA per piece — reduce decision fatigue
  • Always pair with a micro-commitment line if friction is high: "No credit card required." / "Takes 3 minutes."
  • Repeat the CTA near the end — same proposition, slightly different words
  • Use honest time pressure: "while this is fresh on your mind"
  • Always include a guarantee when possible — removes risk

Preemptive Claims

Be the first to say it publicly — even if others do it too (Claude Hopkins' Schlitz strategy). Tour your own factory. Describe the process that every competitor uses, but claim it first. When you say something first, you own it. Don't assume your audience knows what you do behind the scenes.


Page-Specific Guidance

Homepage

  • Serving multiple segments simultaneously. Write for the primary segment, give secondary segments a clear path.
  • Above-the-fold value prop must be the broadest, clearest version of what you do and who it's for.
  • The homepage's job is to pull the right visitor deeper, not to close them.

Landing Page

  • One message. One CTA. Remove navigation if possible.
  • Match the headline exactly to the ad or email that drove the click. Mismatch is the #1 conversion killer.
  • Everything supports the single conversion goal. Remove anything that doesn't.

Pricing Page

  • Core anxiety: "which plan is right for me?" — answer it explicitly.
  • Name plans after outcomes, not sizes. Highlight the recommended plan and justify it.
  • Address price objections directly: ROI framing, guarantee, cost-of-problem comparison.

Feature Page

  • Feature → Benefit → Outcome. Never stop at the feature.
  • Use job-to-be-done framing: "When you need to [situation], [feature] lets you [outcome]."
  • Include proof: before/after, metrics, testimonials tied to that feature.

About Page

  • Tell the story of why this company exists — the founding insight, the gap, the problem the founders lived.
  • Connect the mission to the customer's benefit. "We believe X" only works if X matters to the customer.
  • Still include a CTA. About pages attract high-intent visitors doing diligence.

Copy Review Checklist

Run this on every draft before delivery. Every item must pass.

  1. Who is this for? Can you name the specific reader?
  2. "You" count — talks about the reader, not about you?
  3. First sentence — hooks or bores? Would you keep reading?
  4. Benefit depth — surface benefit or drilled to core desire?
  5. Proof — claims backed by specifics, testimonials, data?
  6. Clarity — read aloud. Any sentence you'd never say to a friend?
  7. Tightness — every paragraph earning its place? Cut ruthlessly.
  8. CTA — one clear action? Reader knows exactly what to do?
  9. Truth — would this embarrass you if the audience knew everything?
  10. Human voice — passes all checks in references/human-voice-rules.md?

Voice and Tone

If .agents/tone-of-voice.md exists, follow it exactly. It overrides all default style assumptions.

If it does not exist, establish formality level and brand personality before writing by asking:

  • Where does this brand sit on the spectrum from formal/corporate to casual/conversational?
  • What three adjectives describe how this brand should sound?
  • What brands does the client admire (even outside their category)?
  • What should this brand never sound like?

Document the answers and apply them consistently. Inconsistent voice erodes trust.


Output Format

Structure every deliverable as follows:

  1. Page copy by section — headline, subheadline, primary CTA, each body section, secondary CTAs, in page order
  2. Annotations — after each major section, 1-2 sentences explaining the key principle applied and why
  3. Alternatives — 2-3 headline variations and 2-3 CTA variations with brief rationale
  4. Meta content — page title (50-60 characters) and meta description (140-160 characters) if relevant
  5. Compliance note at the end of every output: "All output has been checked against references/human-voice-rules.md."

Do not output a wall of copy. Section labels, annotations, and alternatives are not optional.


Key Authorities

AuthorityKnown For
Bill BernbachTruth in advertising
Claude HopkinsScientific Advertising, specificity, preemptive claims
David Ogilvy"You cannot bore people into buying"
Eugene SchwartzBreakthrough Advertising, awareness levels
John CaplesTested Advertising Methods, headline testing
Robert CollierEmotional appeals drive action
Drayton BirdDirect-response, 64 years of tested results
Eddie ShleynerVeryGoodCopy, micro-lessons, narrative structure

Related Skills

  • seo-copywriting — SEO-optimized content: blog posts, pillar pages, product pages, FAQ pages. Keyword strategy, SERP analysis, E-E-A-T signals, featured snippet targeting.
  • french-copywriting — same framework, adapted for French-language copy and French audience conventions
  • social-copywriting — LinkedIn and X (Twitter) post copy: hooks, formats, platform-specific rules
  • tone-of-voice — define brand voice before writing copy, when no voice guide exists yet
  • career-copywriting — CVs, cover letters, LinkedIn profiles, portfolio summaries, application answers, and recruiter-facing positioning
  • copy-editing (external) — line-by-line editing of existing copy without structural rewrites

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.