cro
Skill6 starsChanged 49 days agoMITView on GitHub
When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback.
53 other projects use a version of this, 44 of them edited.
Adopted by
Most recently taken up by
- gaznil/seo-skills-by-gazniledited, first seen Nov 16, 2026
- gaznilmuzammil12-prog/seo-skills-by-gazniledited, first seen Nov 16, 2026
- atpaawej/opencode-skillpackedited, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillsedited, first seen Nov 16, 2026
- undark-ai/Meta-Ads-OSedited, first seen Nov 15, 2026
- alpit-patel/seo-aeo-geo-kitedited, 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 15 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 14 projects that use this
coreyhaines31Skillmarketing-loops
When the user wants a recurring marketing job an AI agent runs on a cadence or trigger, or asks what a weekly or daily automated check should do, remember, and when it should stop: SEO and ads checks, churn watches, outbound triage. For one-off ideas, see marketing-ideas. For the test loop, see ab-testing.
Also in 9 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 16 projects that use this
- +7 more from Cesarjoquin
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 44
- coreyhaines31/marketingskills★ 61k68% same
- Nexus-JPF/note-companion★ 87485% same
- Cesarjoquin/Marketing-Skills★ 19085% same
- Yg0rAndrade/carcara-code★ 8485% same
- open-fox/agents★ 5585% same
- SZcalligrapher/slash-skills-subscription★ 3285% same
- opensite-ai/opensite-skills★ 1585% same
- TommyBez/skillsboard★ 1085% same
- taljeon/plzdo★ 985% same
- anis-dr/skills★ 473% same
34 more not listed
Wrote their own version · 9
- indranilbanerjee/digital-marketing-pro★ 934same name
- alebgl77/claude-inc★ 21same name
- scayver/marketing-skills★ 8same name
- buildwitharup/cortex★ 1same name
- david-corroy/skills-marketing-fr★ 1same name
- donatassimkus/claude-ai-skills★ 1same name
- akachandan1/proofstack★ 0same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
- ZoolCoder/findable★ 0same name
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 repository19 other files it gives its agents.
- campaign-reportSkill
- competitor-intelSkill
- content-auditSkill
- content-strategySkill
- customer-researchSkill
- lead-magnetsSkill
- linkedin-adsSkill
- marketing-councilSkill
- marketing-monthlySkill
- pipeline-analysisSkill
- product-launchSkill
- internal-linkingSkill
- seo-reportSkill
- beautify-github-readmeSkill
- cinemagraphSkill
- frontend-design-anti-slopSkill
- copy-deslopSkill
- copy-longformSkill
- writing-assistantSkill
The file
We split this skill into the rules it gives an agent
9 rules. 5 are common, 4 are distinctive, and 0 are very specific to this project.
5
Common
Most of the 50 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 37
Before providing recommendations, identify:
- Common: line 92
Do images support or distract from the message?
- Common: line 164
Use cases and examples
- Common: line 175
When recommending experiments, consider tests for:
- Common: line 191
Do you have user research, heatmaps, or session recordings?
- Distinctive: line 199
content-strategy: when the page that isn't converting is the sales page at the center of a content program
- Distinctive: line 201
lead-magnets: when the fix is a better offer behind the form
- Distinctive: line 203
frontend-design-anti-slop: when the visual layer is part of the problem
- Distinctive: line 205
Not in this library (upstream has them): signup, popups, ab-testing.
“Common” is measured: kept by at least 6 in 10 of the 50 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
Conversion Rate Optimization (CRO)
Adapted from cro by Corey Haines (MIT). Same method, with this library's rule that company context is scanned, listed, and confirmed before it's read.
Company context: setup step, every run
This skill has no fixed place for company data and never uses context without the user's say-so. Run this before the questions below.
- Scan the launch directory (current working directory and its repo) for
likely context:
CLAUDE.md,AGENTS.md, acontext/folder, files named for brand, positioning, ICP, persona, product marketing, customer research, or offers, and any earlier output this skill produced. List filenames only; don't read contents yet. - Ask one question. Show what was found (or say nothing relevant turned up) and offer four choices: use these files; point me at a different folder or file; paste the context as text; start with no context. Wait.
- Read only what the user approved. A pasted block is the context for this run. "None" means the answers below are the whole picture.
- Still ask the intake questions. Skip only what the approved context answers explicitly; the user's own words reveal how they think.
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Initial Assessment
Before providing recommendations, identify:
- Page Type: Homepage, landing page, pricing, feature, blog, about, other
- Primary Conversion Goal: Sign up, request demo, purchase, subscribe, download, contact sales
- Traffic Context: Where are visitors coming from? (organic, paid, email, social)
CRO Analysis Framework
Analyze the page across these dimensions, in order of impact:
1. Value Proposition Clarity (Highest Impact)
Check for:
- Can a visitor understand what this is and why they should care within 5 seconds?
- Is the primary benefit clear, specific, and differentiated?
- Is it written in the customer's language (not company jargon)?
Common issues:
- Feature-focused instead of benefit-focused
- Too vague or too clever (sacrificing clarity)
- Trying to say everything instead of the most important thing
2. Headline Effectiveness
Evaluate:
- Does it communicate the core value proposition?
- Is it specific enough to be meaningful?
- Does it match the traffic source's messaging?
Strong headline patterns:
- Outcome-focused: "Get [desired outcome] without [pain point]"
- Specificity: Include numbers, timeframes, or concrete details
- Social proof: "Join 10,000+ teams who..."
3. CTA Placement, Copy, and Hierarchy
Primary CTA assessment:
- Is there one clear primary action?
- Is it visible without scrolling?
- Does the button copy communicate value, not just action?
- Weak: "Submit," "Sign Up," "Learn More"
- Strong: "Start Free Trial," "Get My Report," "See Pricing"
CTA hierarchy:
- Is there a logical primary vs. secondary CTA structure?
- Are CTAs repeated at key decision points?
4. Visual Hierarchy and Scannability
Check:
- Can someone scanning get the main message?
- Are the most important elements visually prominent?
- Is there enough white space?
- Do images support or distract from the message?
5. Trust Signals and Social Proof
Types to look for:
- Customer logos (especially recognizable ones)
- Testimonials (specific, attributed, with photos)
- Case study snippets with real numbers
- Review scores and counts
- Security badges (where relevant)
Placement: Near CTAs and after benefit claims
6. Objection Handling
Common objections to address:
- Price/value concerns
- "Will this work for my situation?"
- Implementation difficulty
- "What if it doesn't work?"
Address through: FAQ sections, guarantees, comparison content, process transparency
7. Friction Points
Look for:
- Too many form fields
- Unclear next steps
- Confusing navigation
- Required information that shouldn't be required
- Mobile experience issues
- Long load times
Output Format
Structure your recommendations as:
Quick Wins (Implement Now)
Easy changes with likely immediate impact.
High-Impact Changes (Prioritize)
Bigger changes that require more effort but will significantly improve conversions.
Test Ideas
Hypotheses worth A/B testing rather than assuming.
Copy Alternatives
For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
Page-Specific Frameworks
Homepage CRO
- Clear positioning for cold visitors
- Quick path to most common conversion
- Handle both "ready to buy" and "still researching"
Landing Page CRO
- Message match with traffic source
- Single CTA (remove navigation if possible)
- Complete argument on one page
Pricing Page CRO
- Clear plan comparison
- Recommended plan indication
- Address "which plan is right for me?" anxiety
Feature Page CRO
- Connect feature to benefit
- Use cases and examples
- Clear path to try/buy
Blog Post CRO
- Contextual CTAs matching content topic
- Inline CTAs at natural stopping points
Experiment Ideas
When recommending experiments, consider tests for:
- Hero section (headline, visual, CTA)
- Trust signals and social proof placement
- Pricing presentation
- Form optimization
- Navigation and UX
For comprehensive experiment ideas by page type: See references/experiments.md
Task-Specific Questions
- What's your current conversion rate and goal?
- Where is traffic coming from?
- What does your signup/purchase flow look like after this page?
- Do you have user research, heatmaps, or session recordings?
- What have you already tried?
Related Skills
In this library:
- content-strategy: when the page that isn't converting is the sales page at the center of a content program
- seo-page / seo-report: when traffic, not conversion, is the bottleneck
- lead-magnets: when the fix is a better offer behind the form
- copy-deslop / writing-assistant: for rewriting copy once the structure is right
- frontend-design-anti-slop: when the visual layer is part of the problem
Not in this library (upstream has them): signup, popups, ab-testing.
Form Optimization
For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see references/form.md.
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.

