Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kostja94/conversion-optimization
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy.
Passed 18 of 22 test cases with the skill, and 16 of 22 without it.
and 2 more in the full report
4 fixed14 passed either way2 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have six different ideas to increase checkout conversions, including adding trust seals, simplifying address forms, and adding social proof. Our lead designer wants to pick whichever idea is fastest to build. How should we systematically rank these backlog items before launching tests?
| Checked | Without skill | With skill |
|---|---|---|
| Scores backlog test ideas using Potential, Importance, and Ease dimensions on a 1-10 scale. | Missed | Passed |
The instructions your model reads when the skill loads.
Guides conversion rate optimization (CRO): increasing the percentage of visitors who complete desired actions. Higher conversion rates mean increased revenue, reduced CAC, and better ROI. Use this skill when optimizing funnels, running experiments, or reducing friction on high-traffic pages.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
| Step | Action |
|---|---|
| 1. Research | Map funnel; identify high-traffic, low-conversion pages |
| 2. Hypothesize | Form testable hypothesis (if X, then Y because Z) |
| 3. Prioritize | Score by Potential, Importance, Ease (PIE) |
| 4. Test | A/B or multivariate; adequate sample size |
| 5. Analyze | Statistical significance; implement winner |
Score each test idea 1–10:
| Factor | Question |
|---|---|
| Potential | How much improvement is possible? |
| Importance | How much traffic does this page get? |
| Ease | How easy to implement? |
Rank backlog by total score; run highest-impact tests first.
test cases passed, vs 16 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.