[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AV3HJY1G6VZ95AH4ZZBY3":3,"skill-same:01M71AV3HJY1G6VZ95AH4ZZBY3":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71AV3HJY1G6VZ95AH4ZZBY3","conversion-optimization",null,"When the user wants to improve conversion rates, run A\u002FB tests, optimize funnels, or reduce friction. Also use when the user mentions \"CRO\", \"conversion rate optimization\", \"A\u002FB test\" or \"split test\". For pricing psychology, use pricing-strategy.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fstrategies\u002Flaunch\u002Fconversion\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"conversion optimization","conversion","Optimization","friction","run","optimize","test","conversion rate optimization","pricing psychology","split","reduce","when","use","psychology","strategy","tests","improve","pricing","for","cro","2026-11-10 10:12:30",false,"---\nname: conversion-optimization\ndescription: When the user wants to improve conversion rates, run A\u002FB tests, optimize funnels, or reduce friction. Also use when the user mentions \"CRO\", \"conversion rate optimization\", \"A\u002FB test\" or \"split test\". For pricing psychology, use pricing-strategy.\nmetadata:\n  version: 1.1.1\n---\n\n# Strategies: Conversion Optimization\n\nGuides 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.\n\n**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.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read Sections 4 (Audience), 5 (Website), 6 (Keywords).\n\nIdentify:\n1. **Funnel stage**: Awareness, consideration, decision, post-purchase\n2. **Conversion goal**: Signup, purchase, download, demo request\n3. **Traffic**: Volume; mobile vs desktop split\n4. **Current conversion rate**: Baseline for improvement\n\n## CRO Process\n\n| Step | Action |\n|------|--------|\n| **1. Research** | Map funnel; identify high-traffic, low-conversion pages |\n| **2. Hypothesize** | Form testable hypothesis (if X, then Y because Z) |\n| **3. Prioritize** | Score by Potential, Importance, Ease (PIE) |\n| **4. Test** | A\u002FB or multivariate; adequate sample size |\n| **5. Analyze** | Statistical significance; implement winner |\n\n## PIE Prioritization Framework\n\nScore each test idea 1–10:\n\n| Factor | Question |\n|--------|----------|\n| **Potential** | How much improvement is possible? |\n| **Importance** | How much traffic does this page get? |\n| **Ease** | How easy to implement? |\n\nRank backlog by total score; run highest-impact tests first.\n\n## A\u002FB Testing Best Practices\n\n| Practice | Guideline |\n|----------|-----------|\n| **Sample size** | Calculate minimum before launch; 95% significance without adequate sample = false positives |\n| **Duration** | Run full week cycles; account for day-of-week effects |\n| **One variable** | Test one element per experiment (or use MVT for multiple) |\n| **Mobile separate** | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ |\n| **Low traffic** | Use Bayesian testing for faster, actionable results |\n\n## Key Testing Areas\n\n| Page Type | Test Ideas |\n|-----------|------------|\n| **Homepage** | Search bar prominence; personalized content; hero CTA; social proof placement |\n| **Landing page** | Headline; form length; CTA copy; above-fold layout |\n| **Product\u002FCategory** | Quick view; descriptions; add-to-cart placement |\n| **Checkout** | Form fields; progress indicator; trust badges; guest checkout |\n| **Pricing** | Plan order; anchoring; CTA per tier |\n\n**Personalization**: Personalized experiences generate ~41% more impact than generic ones.\n\n## Commercialization Infrastructure\n\n| Module | Purpose |\n|--------|---------|\n| **Data & BI** | Data warehouse; user behavior events; agile surveys |\n| **A\u002FB testing** | Experiment platform; statistical significance; backend-controlled variants |\n| **User education** | Help docs (multi-language); update notifications; EDM |\n| **Attribution** | Ad pixels; attribution model; impression-to-click-to-sale tracking |\n\n**Avoid**: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats.\n\n## Foundational Requirements\n\n- **Analytics**: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis)\n- **Qualitative**: Heatmaps, session recordings, user tests—understand *why* drop-off occurs\n- **Technical**: Dedicated resources for 2–4 tests\u002Fmonth; maintain momentum\n\n## Output Format\n\n- **Funnel map** (stages, conversion rates, drop-off)\n- **Hypothesis** (if X, then Y because Z)\n- **Test plan** (variant, metric, sample size, duration)\n- **Implementation** checklist\n\n## Related Skills\n\n- **landing-page-generator**: Landing page structure and copy\n- **cta-generator**: CTA design and placement\n- **analytics-tracking**: GA4, events, conversion tracking\n- **traffic-analysis**: Attribution, funnel analysis\n- **copywriting**: Headline, CTA copy for tests\n","# Strategies: Conversion Optimization\n\nGuides 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.\n\n**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.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read Sections 4 (Audience), 5 (Website), 6 (Keywords).\n\nIdentify:\n1. **Funnel stage**: Awareness, consideration, decision, post-purchase\n2. **Conversion goal**: Signup, purchase, download, demo request\n3. **Traffic**: Volume; mobile vs desktop split\n4. **Current conversion rate**: Baseline for improvement\n\n## CRO Process\n\n| Step | Action |\n|------|--------|\n| **1. Research** | Map funnel; identify high-traffic, low-conversion pages |\n| **2. Hypothesize** | Form testable hypothesis (if X, then Y because Z) |\n| **3. Prioritize** | Score by Potential, Importance, Ease (PIE) |\n| **4. Test** | A\u002FB or multivariate; adequate sample size |\n| **5. Analyze** | Statistical significance; implement winner |\n\n## PIE Prioritization Framework\n\nScore each test idea 1–10:\n\n| Factor | Question |\n|--------|----------|\n| **Potential** | How much improvement is possible? |\n| **Importance** | How much traffic does this page get? |\n| **Ease** | How easy to implement? |\n\nRank backlog by total score; run highest-impact tests first.\n\n## A\u002FB Testing Best Practices\n\n| Practice | Guideline |\n|----------|-----------|\n| **Sample size** | Calculate minimum before launch; 95% significance without adequate sample = false positives |\n| **Duration** | Run full week cycles; account for day-of-week effects |\n| **One variable** | Test one element per experiment (or use MVT for multiple) |\n| **Mobile separate** | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ |\n| **Low traffic** | Use Bayesian testing for faster, actionable results |\n\n## Key Testing Areas\n\n| Page Type | Test Ideas |\n|-----------|------------|\n| **Homepage** | Search bar prominence; personalized content; hero CTA; social proof placement |\n| **Landing page** | Headline; form length; CTA copy; above-fold layout |\n| **Product\u002FCategory** | Quick view; descriptions; add-to-cart placement |\n| **Checkout** | Form fields; progress indicator; trust badges; guest checkout |\n| **Pricing** | Plan order; anchoring; CTA per tier |\n\n**Personalization**: Personalized experiences generate ~41% more impact than generic ones.\n\n## Commercialization Infrastructure\n\n| Module | Purpose |\n|--------|---------|\n| **Data & BI** | Data warehouse; user behavior events; agile surveys |\n| **A\u002FB testing** | Experiment platform; statistical significance; backend-controlled variants |\n| **User education** | Help docs (multi-language); update notifications; EDM |\n| **Attribution** | Ad pixels; attribution model; impression-to-click-to-sale tracking |\n\n**Avoid**: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats.\n\n## Foundational Requirements\n\n- **Analytics**: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis)\n- **Qualitative**: Heatmaps, session recordings, user tests—understand *why* drop-off occurs\n- **Technical**: Dedicated resources for 2–4 tests\u002Fmonth; maintain momentum\n\n## Output Format\n\n- **Funnel map** (stages, conversion rates, drop-off)\n- **Hypothesis** (if X, then Y because Z)\n- **Test plan** (variant, metric, sample size, duration)\n- **Implementation** checklist\n\n## Related Skills\n\n- **landing-page-generator**: Landing page structure and copy\n- **cta-generator**: CTA design and placement\n- **analytics-tracking**: GA4, events, conversion tracking\n- **traffic-analysis**: Attribution, funnel analysis\n- **copywriting**: Headline, CTA copy for tests\n",{"name":5,"metadata":49,"description":7},{"version":50},"1.1.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fstrategies\u002Flaunch\u002Fconversion",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-01 12:36:50",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add ariadoss\u002Fsuperskills --skill conversion-optimization",{"tool":67,"command":68},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill conversion-optimization",{"tool":70,"command":71},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill conversion-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fstrategies\u002Flaunch\u002Fconversion\u002FSKILL.md",true,[],[76,101,125,144,172,188],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":44},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[78,86,87,88,89,90,91,92,93,35,94,95,96,97,98,36,99,100],"user","download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":44},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[108,109,89,110,111,112,113,114,115,35,116,117,118,119,120,42,121,122,123,124],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":44},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[127,132,133,134,36,135,136,137,138,139,140,111,141,35,142,143],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"publishedAt":44},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[154,155,156,157,158,159,29,160,161,35,162,163,164,165,166,167,168,169,170,171],"web","perf","web perf","resources","MCP","layout","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":44},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[174,119,179,180,140,111,181,182,35,183,36,184,185,186,187],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":44},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[195,196,197,198,199,200,30,35,201,36,202],"validate","idea","validate idea","framework","it","minimalist","business","before building"]