/conversion
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
$ npx -y skills add kostja94/marketing-skills --skill conversion --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/conversion
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
conversion.SKILL.mdname: conversion-optimization
description: 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.
metadata:
version: 1.1.1
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
Read more
name: conversion-optimization description: 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. metadata: version: 1.1.1
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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill