Individual skill
landing-page-cro
Improves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.
skills/landing-page-cro/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Landing Page CRO
Conversion rate optimization is not applying best practices - it is forming specific hypotheses from real user evidence, testing them, and iterating. The costly failure this skill prevents is the redesign roulette: shipping a batch of untested "improvements" that mixes winners with losers, moves nothing, and teaches nothing, while paid spend keeps landing on a leaky page.
## Operating procedure
Order is strict: audit before hypotheses (a hypothesis without an observation is a guess), hypotheses before prioritization, prioritization before tests, and significance before verdicts.
### Step 1: Gather inputs
Collect before auditing. Label anything assumed as a guess.
1. Page URL and its single conversion goal (form fill, purchase, signup). A page with two goals is already a finding.
2. Current CVR and traffic: unique visitors per week and conversions per week - these decide the testing method in Step 5.