copywriting
Skill43 starsChanged 4 months agoMITView on GitHub
Use when writing or rewriting website copy: homepages, landing pages, pricing pages, product pages, feature pages, hero sections, headlines, subheads, CTAs, value propositions, taglines, and above-the-fold messaging. Do not use for email sequences, blog posts, longform X articles, or platform-specific ad copy.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- figueroaignacio/ignaciofigueroa.devtheir own version, first seen Nov 8, 2026
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.
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 · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- supabase/supabase★ 115ksame name
- coreyhaines31/marketingskills★ 59ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- stagewise-io/stagewise★ 6.8ksame name
- ZJU-REAL/Easel★ 4.5ksame name
- legions-developer/evilcharts★ 3.2ksame name
- compozy/compozy★ 2.9ksame name
- databuddy-analytics/Databuddy★ 1.2ksame name
- KartikLabhshetwar/screenshot-studio★ 1.1ksame name
- KartikLabhshetwar/stage★ 1.1ksame name
181 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 repository25 other files it gives its agents.
- ab-testingSkill
- ai-seoSkill
- analytics-trackingSkill
- cold-outreachSkill
- competitor-analysisSkill
- content-strategySkill
- creative-briefSkill
- cro-auditSkill
- customer-researchSkill
- distribution-planSkill
- ecommerce-app-croSkill
- email-sequenceSkill
- goalSkill
- launch-loop-strategySkill
- launch-strategySkill
- marketing-briefSkill
- marketing-planSkill
- offer-designSkill
- paid-adsSkill
- partnershipsSkill
- positioningSkill
- retentionSkill
- sales-enablementSkill
- seo-strategySkill
- x-article-writerSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
6
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
- Distinctive: line 8
Write clear website and landing-page copy that makes a strong promise and backs it up with proof.
- Distinctive: line 18
Do not use this for:
- Very specific: line 25
Before asking questions, read existing product-marketing context if present: .agents/product-marketing.md, .claude/product-marketing.md, or …
- Distinctive: line 29
Look for or ask for:
- Distinctive: line 39
If proof is missing, write lower-claim copy and mark where proof is needed.
- Distinctive: line 43
Create the page argument before writing polished prose:
- Distinctive: line 51
Every section should move the reader closer to the action.
“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.
Files
Copywriting
Write clear website and landing-page copy that makes a strong promise and backs it up with proof.
Scope
Use this for:
- Homepage, landing page, pricing page, feature page, product page, and about page copy.
- Hero headline, subheadline, CTA, value proposition, tagline, section copy, and objection handling.
- Rewriting weak page copy to make it clearer and more persuasive.
Do not use this for:
- Email flows or lifecycle messages. Use
email-sequence. - Blog posts, SEO articles, or content calendars. Use
content-strategyorseo-strategy. - Longform X/Twitter articles. Use
x-article-writer. - Platform-specific Google, Meta, or LinkedIn ad copy. Use
creative-brieforpaid-ads.
Before asking questions, read existing product-marketing context if present: .agents/product-marketing.md, .claude/product-marketing.md, or product-marketing-context.md.
Copy Inputs
Look for or ask for:
- Target reader and traffic source.
- Desired action.
- Offer or product being sold.
- Current page or draft.
- Proof: numbers, customers, testimonials, demos, screenshots, case studies.
- Objections and alternatives.
- Tone constraints.
If proof is missing, write lower-claim copy and mark where proof is needed.
Build The Argument
Create the page argument before writing polished prose:
- Reader arrives with this belief.
- The page must change that belief to this.
- The strongest promise is this.
- The proof is this.
- The next action is this.
Every section should move the reader closer to the action. Remove claims that do not support the argument.
Match Claims To Proof
For every meaningful claim, define:
- Claim.
- Proof type: customer quote, metric, demo, screenshot, credential, example, guarantee, comparison.
- Proof strength: weak, usable, strong, publishable.
- Allowed wording ceiling: what can be said honestly without overstating.
- Placement: hero, proof block, FAQ, CTA area, pricing, section body.
- Gap: what proof is missing.
Write The Copy
Use:
- Specific outcomes over soft adjectives.
- Concrete nouns and verbs.
- Customer language where available.
- Short sections with one job each.
- CTAs that state what happens next.
- Objection handling near the point of hesitation.
Avoid:
- Empty superiority claims.
- Unsupported numbers.
- Clever lines that hide the offer.
- Exclamation marks as intensity.
- Feature dumps without user consequence.
Page Notes
- Homepage: explain the product and create clear paths for different visitors.
- Landing page: one audience, one promise, one primary CTA.
- Pricing page: help the buyer choose, reduce risk, and explain plan differences.
- Feature/product page: connect feature, use case, proof, and outcome.
- About page: tell the story only where it strengthens trust or conversion.
Output
Copy strategy:
Reader:
Current belief:
Desired belief:
Primary promise:
Proof:
Action:
Claim and proof table:
| Claim | Proof type | Strength | Wording ceiling | Placement | Gap |
Draft:
Headline options:
1. [headline]
2. [headline]
3. [headline]
Hero headline:
Subhead:
Primary CTA:
Secondary CTA:
CTA options:
- [option]
- [option]
Section flow:
1. [section name]
Copy:
Why it exists:
Objection answers:
- [objection] -> [copy]
Proof gaps:
- [claim needing evidence]
Optional SEO:
Title:
Meta description: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.

