agentleFS
Sign inStart free
buildwitharupbuildwitharup/cortex/skills/cro/SKILL.md

cro

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the user wants to improve conversion rates on landing pages, forms, signup flows, or in-app upgrade moments. Also triggers on "improve conversion rate", "landing page optimization", "why aren't people converting", "form optimization", "CRO audit", "A/B test ideas", "increase signups".

48 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • 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 15 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 14 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 11 projects that use this

  • coreyhaines31Skill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'weekly ads check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'run my SEO,' 'SEO operator,' 'daily SEO agent,' 'run my outbound,' 'AI SDR,' 'reply triage,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 9 projects that use this

  • +7 more from Cesarjoquin

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 45 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
  1. Very specific:

    Check for product marketing context at .agents/product-marketing.md or .claude/product-marketing.md.

    line 29
  2. Distinctive:

    When optimizing the free-to-paid upgrade moment inside a product:

    line 69
  3. Distinctive:

    When user hits a usage limit — show the limit clearly, offer upgrade immediately

    line 78
  4. Distinctive:

    When user tries a premium feature — let them try it, then gate at save/export

    line 79
  5. Distinctive:

    After activation moment — "You're getting value — keep it going"

    line 80
  6. Distinctive:

    Use call tracking (WhatConverts, CallRail) to attribute calls to campaigns

    line 93
  7. Distinctive:

    Test these in order — highest impact first:

    line 101

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

CRO (Enhanced)

Attribution: Enhanced from coreyhaines31/marketingskills (MIT). Enhancements: automotive dealership high-volume B2C conversion patterns, PLG SaaS in-app upgrade flow optimization, phone and form dual-track for businesses where both matter.

Role

You are an expert conversion rate optimization strategist. Your goal is to identify why visitors are not converting and recommend specific, testable changes — grounded in behavior, not opinions.

When to use this skill

  • User wants to improve landing page conversion rates
  • User has traffic but low form submissions or signups
  • User wants to optimize a free-to-paid upgrade flow
  • User needs A/B test ideas
  • User mentions "CRO", "conversion rate", "landing page", "why aren't people signing up"

Context check

Check for product marketing context at .agents/product-marketing.md or .claude/product-marketing.md. Use ICP, offer, and conversion goal before making any recommendations.

CRO audit framework

Above the fold (first screen, no scroll)

  • Headline states the outcome — not the feature
  • Subheadline answers "for who" and "how"
  • One primary CTA — not three buttons competing
  • CTA is specific — "Start free trial" not "Get started"
  • Social proof visible — logos, numbers, or a quote
  • No navigation menu (landing pages only — remove it)

Trust signals

  • Real company name and address visible
  • Customer logos or named testimonials
  • Specific numbers — "2,400 customers" not "thousands"
  • Security badges if handling payments or sensitive data
  • Guarantee or risk reversal ("Cancel anytime", "Free for 14 days")

Form optimization

  • Minimum fields — ask only what you need now
  • Field labels above inputs — not placeholder text only
  • Error messages explain how to fix — not just "invalid"
  • CTA button on form is specific — "Create my account" not "Submit"
  • Mobile keyboard type matches input (email keyboard for email field)

Automotive / high-volume B2C patterns

High-intent buyers in automotive and similar high-ticket B2C move fast and want to talk:

  • Phone number prominent — above the fold, clickable on mobile
  • Form and phone dual-track — offer both, let the buyer choose
  • Urgency is real — "3 units left" works when it's true, never fabricate
  • Specific inventory — show the actual vehicle / product, not a generic image
  • Financing CTA — "Get pre-approved" converts better than "Contact us" in automotive
  • Google reviews count — display star rating and review count prominently
  • Chat widget — high-intent buyers want instant answers, not a callback tomorrow

PLG SaaS in-app upgrade patterns

When optimizing the free-to-paid upgrade moment inside a product:

Paywall design:

  • Show what they get, not what they lose
  • One upgrade plan highlighted — not a confusing comparison table
  • Annual vs monthly toggle — default to annual
  • "Most popular" badge on recommended plan

Upgrade trigger moments:

  • When user hits a usage limit — show the limit clearly, offer upgrade immediately
  • When user tries a premium feature — let them try it, then gate at save/export
  • After activation moment — "You're getting value — keep it going"
  • Trial day 11 — 3 days left warning in-app, not just email

Friction reducers:

  • One-click upgrade if card is already on file
  • "Try for free for 7 days" beats "Upgrade now" for hesitant users
  • Show current plan vs upgraded plan side by side

Phone and form dual-track

For businesses where both phone and form conversions matter:

  • Track phone clicks as GA4 conversion events (not just form submissions)
  • Use call tracking (WhatConverts, CallRail) to attribute calls to campaigns
  • Different CTA for different intent levels:
    • High intent: "Call now" or "Book today"
    • Research phase: "Get a quote" or "See pricing"
  • A/B test: same page with phone CTA prominent vs form CTA prominent

A/B test priority order

Test these in order — highest impact first:

  1. Headline (biggest lever — test first)
  2. CTA button text and color
  3. Social proof type (logos vs testimonials vs numbers)
  4. Form length (fewer fields vs more fields)
  5. Hero image (person vs product vs abstract)
  6. Pricing presentation (monthly vs annual default)

Related skills

  • copywriting — for the headline and copy that drives conversion
  • plg-onboarding — for the full free-to-paid activation flow
  • ads — for the paid traffic landing on these pages
  • ga4-attribution — for measuring conversion outcomes

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.

Check your setup, free