Agent skill · Security

cro-optimization

Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions. Use this skill whenever the user wants to optimize conversion, run A/B tests, audit a funnel, generate test hypotheses, design experiments, or analyze test results. Triggers on conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization. Also triggers when the user has a conversion problem and isn't sure where to

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill cro-optimization --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/cro-optimization/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CRO Optimization Run conversion rate optimization as a structured discipline: audit → hypothesize → test → decide. Stack-agnostic. Tool-agnostic. This skill is for running tests against existing pages and flows. For writing landing page copy from scratch, use `landing-page-copy`. For setting up the analytics that make CRO possible, use `analytics-strategy`. --- ## When to use - Converting traffic at lower rate than expected - Specific funnel step has high drop-off - Pages with high traffic that could move the needle if optimized - A/B testing infrastructure exists (or can be set up) - Statistical significance and sample size questions ## When NOT to use - Without sufficient traffic to test (under ~5,000 monthly conversions per variant) - Pre-launch (no users to test on yet) - Strategy or messaging-level questions that need qualitative research first - Brand-defining choices (CRO can't optimize a fundamentally wrong brand) --- ## Required inputs - The page or flow under optimization - Current conversion rate and traffic volume - Access to analytics (event tracking, funnel data) - An A/B testing tool (or willingness to set one up) - Time and budget for testing (typically 2 to 8 wee

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 4 phases
  5. 1. Audit
  6. 2. Hypothesis
  7. 3. Test design
  8. 4. Decide
  9. Statistical foundations
  10. Significance and confidence
  11. Sample size
  12. Multiple testing
  13. Workflow
  14. Failure patterns
Ships with 1 file
  • references/hypothesis-library.md
More from claude-skills
All skills →
About this skill
What does the cro-optimization skill do?

Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions. Use this skill whenever the user wants to optimize conversion, run A/B tests, audit a funnel, generate test hypotheses, design experiments, or analyze test results. Triggers on conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization. Also triggers when the user has a conversion problem and isn't sure where to

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill cro-optimization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going