Conversion Optimization
Install this skill when you need a structured CRO workflow—research, hypotheses, A/B tests, and friction fixes—for signup, checkout, or demo funnels.
Overview
Conversion Optimization is an agent skill most often used in Grow (also Validate landing, Launch distribution) that guides funnel research, experiment planning, and friction reduction to lift conversion rates.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill conversion-optimizationWhat is this skill?
- Initial assessment: funnel stage, conversion goal, traffic split, baseline rate
- CRO process table from research through experiment design and implementation
- Triggers on CRO, A/B/split tests, funnel, checkout, and form optimization keywords
- Reads project-context audience, website, and keyword sections when present
- Explicit handoff to pricing-strategy for pricing psychology (not CRO scope)
Adoption & trust: 1k installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have traffic and a conversion goal but no disciplined process to find friction, prioritize tests, and measure lift against a baseline.
Who is it for?
Solo builders optimizing SaaS signups, ecommerce checkout, or high-traffic landing pages with measurable baselines.
Skip if: Pure pricing psychology or packaging decisions without funnel or experiment work—use pricing-strategy instead.
When should I use this skill?
User wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction; mentions CRO, split test, checkout/form optimization, or conversion funnel.
What do I get? / Deliverables
You leave with a mapped funnel stage, baseline metrics, and a structured CRO process aligned to your signup, purchase, or demo goal.
- Funnel-stage assessment
- CRO process plan aligned to research and experiments
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Conversion optimization compounds revenue after traffic exists, so the canonical shelf is Grow; it also applies earlier on landing and checkout pages during Validate and Launch. Lifecycle covers funnel stages from consideration through purchase and post-purchase, matching the skill’s funnel-stage assessment and conversion goals.
Where it fits
Prioritize form and CTA friction fixes on a pre-launch landing page before scaling ad spend.
Tune campaign landing paths so paid traffic converts on demo or download goals.
Run split tests across signup and onboarding steps to lower CAC on existing traffic.
Optimize content CTAs and mid-funnel pages for consideration-stage visitors.
How it compares
Structured CRO workflow skill, not a one-off copy critique or generic SEO keyword pass.
Common Questions / FAQ
Who is conversion-optimization for?
Indie and solo builders who ship landing pages, checkouts, or signup flows and want agent-guided CRO steps rather than ad-hoc UI guesses.
When should I use conversion-optimization?
During Validate when tuning landing pages, Launch when improving campaign destinations, and Grow when optimizing lifecycle funnels, forms, checkout, or running A/B and split tests.
Is conversion-optimization safe to install?
Review the Security Audits panel on this Prism page and your repo’s skill source before trusting third-party marketing skills in production workflows.
SKILL.md
READMESKILL.md - Conversion Optimization
# Strategies: Conversion Optimization 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. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 4 (Audience), 5 (Website), 6 (Keywords). Identify: 1. **Funnel stage**: Awareness, consideration, decision, post-purchase 2. **Conversion goal**: Signup, purchase, download, demo request 3. **Traffic**: Volume; mobile vs desktop split 4. **Current conversion rate**: Baseline for improvement ## CRO Process | 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 | ## PIE Prioritization Framework 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. ## A/B Testing Best Practices | Practice | Guideline | |----------|-----------| | **Sample size** | Calculate minimum before launch; 95% significance without adequate sample = false positives | | **Duration** | Run full week cycles; account for day-of-week effects | | **One variable** | Test one element per experiment (or use MVT for multiple) | | **Mobile separate** | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ | | **Low traffic** | Use Bayesian testing for faster, actionable results | ## Key Testing Areas | Page Type | Test Ideas | |-----------|------------| | **Homepage** | Search bar prominence; personalized content; hero CTA; social proof placement | | **Landing page** | Headline; form length; CTA copy; above-fold layout | | **Product/Category** | Quick view; descriptions; add-to-cart placement | | **Checkout** | Form fields; progress indicator; trust badges; guest checkout | | **Pricing** | Plan order; anchoring; CTA per tier | **Personalization**: Personalized experiences generate ~41% more impact than generic ones. ## Commercialization Infrastructure | Module | Purpose | |--------|---------| | **Data & BI** | Data warehouse; user behavior events; agile surveys | | **A/B testing** | Experiment platform; statistical significance; backend-controlled variants | | **User education** | Help docs (multi-language); update notifications; EDM | | **Attribution** | Ad pixels; attribution model; impression-to-click-to-sale tracking | **Avoid**: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats. ## Foundational Requirements - **Analytics**: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis) - **Qualitative**: Heatmaps, session recordings, user tests—understand *why* drop-off occurs - **Technical**: Dedicated resourc