agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/copywriting/SKILL.md

copywriting

Skill9 starsChanged 6 months agoMITView on GitHub

Write, rewrite, or improve marketing copy for any page — homepage, landing pages, pricing pages, feature pages, about pages. Also use for "write copy for," "improve this copy," "headline help," "CTA copy," "value proposition," "tagline," "hero section copy," "above the fold." For email copy, see email-sequence. For product positioning statement, see positioning-messaging.

191 other projects use a version of this, 136 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

We split this skill into the rules it gives an agent

9 rules. 3 are common, 2 are distinctive, and 4 are very specific to this project.

  • 3

    Common

    Most of the 179 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.

    line 9
  2. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 11
  3. Very specific:

    If MEMORY.md contains product context (wedge, ICP, competitors), use it.

    line 22
  4. Distinctive:

    If you have to choose between clear and creative, choose clear.

    line 51
  5. Common:

    Use words your customers use.

    line 61
  6. Common:

    Create Your First [Thing]

    line 155
  7. Very specific:

    Write for the job the customer is hiring the product to do, not the feature.

    line 205
  8. Very specific:

    After writing copy, check against humanizer patterns:

    line 217
  9. Common:

    When writing copy, provide:

    line 245

“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

[YOUR_PRODUCT] Context

Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint. Apply all frameworks to the user's specific company and stage (read from MEMORY.md). Follow output preferences from USER.md (language, format, platform constraints). For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.

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 MEMORY.md contains product context (wedge, ICP, competitors), use it. Only ask for information not already covered.

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.

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

  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 — Fabricated statistics or testimonials erode trust and create legal liability

Quick Quality Check

  • Jargon that could confuse outsiders?
  • Sentences trying to do too much?
  • Passive voice constructions?
  • Exclamation points? (remove them)
  • Marketing buzzwords without substance?

Best Practices

Be Direct

Get to the point. Don't bury the value in qualifications.

Use Rhetorical Questions

Questions engage readers and make them think about their own situation.

  • "Tired of chasing approvals?"

Use Analogies When Helpful

Analogies make abstract concepts concrete and memorable.


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

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

SectionPurpose
Social ProofBuild credibility (logos, stats, testimonials)
Problem/PainShow you understand their situation
Solution/BenefitsConnect to outcomes (3-5 key benefits)
How It WorksReduce perceived complexity (3-4 steps)
Objection HandlingFAQ, comparisons, guarantees
Final CTARecap 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]


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

Psychological Triggers

Apply these principles where they fit naturally. Don't force all of them into every page.

Social proof

Show that others trust you. Logos, user counts, testimonials, case studies. Place social proof immediately after the hero section to reduce skepticism early.

Loss aversion

People fear losing more than they desire gaining. "Stop losing [valuable thing your customer cares about]" hits harder than "Gain better [thing]." Frame the cost of inaction.

Specificity = credibility

"83% faster month-end close" beats "significantly faster." "Teams with 50+ [resources]" beats "large [team type]." Vague claims feel like marketing; specific claims feel like data.

JTBD framing

Write for the job the customer is hiring the product to do, not the feature. Not "[YOUR_CORE_TECH]-powered [feature]" but "[Outcome-focused promise in plain language]."

Cognitive load reduction

Fewer choices = more conversions. One CTA per section. Simple language. Short paragraphs. Don't make the reader think about navigation — make the next step obvious.

Anchoring

Show the expensive/painful alternative first. "Your team spends 4 hours/week on [painful task]. [YOUR_PRODUCT]: $250/month." The anchor makes the price feel small.


Humanizer integration

After writing copy, check against humanizer patterns:

  • Does it read like AI output? (inflated significance, promotional language, rule of three)
  • Any AI vocabulary? (pivotal, landscape, foster, delve, showcase, vibrant)
  • Generic conclusions? ("The future of..." — replace with specific next step)
  • Sycophantic tone? (cut enthusiasm, add substance)

Landing page copy that reads as AI-generated erodes trust. Run humanizer on final drafts.


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?

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]
  • Option B: [copy] — [rationale]

Meta Content (if relevant)

  • Page title (for SEO)
  • Meta description

Related Skills

  • social-writer: For adapting ideas into LinkedIn/X posts (copywriting handles web pages; social-writer handles social distribution)
  • humanizer: For removing AI patterns from finished copy — run on final drafts
  • email-sequence: For email copywriting and nurture flows
  • positioning-messaging: For product positioning and value props
  • brand-storytelling: For company narrative and pitch story
  • content-strategy: For deciding what content to produce
  • seo-audit: For SEO optimization of pages (includes GEO for AI search)
  • programmatic-seo: For SEO pages at scale

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.