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.
Best use case
conversion-optimization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using conversion-optimization should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/conversion/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How conversion-optimization Compares
| Feature / Agent | conversion-optimization | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 resources for 2–4 tests/month; maintain momentum ## Output Format - **Funnel map** (stages, conversion rates, drop-off) - **Hypothesis** (if X, then Y because Z) - **Test plan** (variant, metric, sample size, duration) - **Implementation** checklist ## Related Skills - **landing-page-generator**: Landing page structure and copy - **cta-generator**: CTA design and placement - **analytics-tracking**: GA4, events, conversion tracking - **traffic-analysis**: Attribution, funnel analysis - **copywriting**: Headline, CTA copy for tests
Related Skills
generative-engine-optimization
When the user wants to optimize for AI search visibility (ChatGPT, Claude, Perplexity, AI Overviews). Also use when the user mentions "GEO," "AEO," "generative engine optimization," "AI search visibility," "LLM optimization," "GitHub GEO," "Grokipedia," "optimize for ChatGPT," "AI Overviews," "Bing Copilot," "Yandex AI," "Perplexity optimization," "GEO strategy," or "AI search optimization." For third-party publishing strategy (which platforms to use), use parasite-seo. For GitHub repos, README, and Awesome lists, use github. For Medium.com only, use medium-posts. For Grokipedia edits, use grokipedia-recommendations. For traditional Google SERP strategy, use seo-strategy.
video-optimization
When the user wants to optimize videos for Google Search, video sitemap, VideoObject schema, or video SEO on websites. Also use when the user mentions "video SEO," "video sitemap," "VideoObject," "video thumbnail," "video indexing," "video preview," "key moments," "Clip schema," or "embedded video optimization." For page template, use article-page-generator.
image-optimization
When the user wants to optimize images for search engines and performance. Also use when the user mentions "image SEO," "alt text," "image captions," "figcaption," "image optimization," "WebP," "lazy loading," "LCP," "image sitemap," "responsive images," "srcset," "image format," or "hero image optimization." For CWV, use core-web-vitals.
content-optimization
When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content structure." For keywords, use keyword-research.
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.