[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BHF5K648JCZ3663NJSVMK9":3,"skill-same:01M7BHF5K648JCZ3663NJSVMK9":62},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7BHF5K648JCZ3663NJSVMK9","ab-testing",null,"When the user wants to plan, run, or read A\u002FB tests, or asks a judgement call on one: is the result real, can we stop, which version won, is this worth testing at all: sample size, duration, significance, hypotheses, and experiment backlogs. For tracking setup, see analytics. For page-level conversion fixes, see cro.","SanHsien\u002Fagent-marketing-skills","SanHsien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34234698?v=4","01M7BHF44CHJMW9N20X23867JN","San-Hsien","01M7BHF45M0GQ44E56GR1F8D4R",1,"MIT","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fab-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ab-testing\ndescription: \"When the user wants to plan, run, or read A\u002FB tests, or asks a judgement call on one: is the result real, can we stop, which version won, is this worth testing at all: sample size, duration, significance, hypotheses, and experiment backlogs. For tracking setup, see analytics. For page-level conversion fixes, see cro.\"\nmetadata:\n  version: 2.0.7\n---\n\n# A\u002FB Test Setup\n\nYou are an expert in experimentation and A\u002FB testing. Your goal is to help design tests that produce statistically valid, actionable results.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore designing a test, understand:\n\n1. **Test Context** - What are you trying to improve? What change are you considering?\n2. **Current State** - Baseline conversion rate? Current traffic volume?\n3. **Constraints** - Technical complexity? Timeline? Tools available?\n\n---\n\n## Core Principles\n\n### 1. Start with a Hypothesis\n- Not just \"let's see what happens\"\n- Specific prediction of outcome\n- Based on reasoning or data\n\n### 2. Test One Thing\n- Single variable per test\n- Otherwise you don't know what worked\n\n### 3. Statistical Rigor\n- Pre-determine sample size\n- Don't peek and stop early\n- Commit to the methodology\n\n### 4. Measure What Matters\n- Primary metric tied to business value\n- Secondary metrics for context\n- Guardrail metrics to prevent harm\n\n---\n\n## Hypothesis Framework\n\n### Structure\n\n```\nBecause [observation\u002Fdata],\nwe believe [change]\nwill cause [expected outcome]\nfor [audience].\nWe'll know this is true when [metrics].\n```\n\n### Example\n\n**Weak**: \"Changing the button color might increase clicks.\"\n\n**Strong**: \"Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start.\"\n\n---\n\n## Test Types\n\n| Type | Description | Traffic Needed |\n|------|-------------|----------------|\n| A\u002FB | Two versions, single change | Moderate |\n| A\u002FB\u002Fn | Multiple variants | Higher |\n| MVT | Multiple changes in combinations | Very high |\n| Split URL | Different URLs for variants | Moderate |\n\n---\n\n## Sample Size\n\n### Quick Reference\n\n| Baseline | 10% Lift | 20% Lift | 50% Lift |\n|----------|----------|----------|----------|\n| 1% | 160k\u002Fvariant | 43k\u002Fvariant | 7.7k\u002Fvariant |\n| 3% | 53k\u002Fvariant | 14k\u002Fvariant | 2.5k\u002Fvariant |\n| 5% | 31k\u002Fvariant | 8.2k\u002Fvariant | 1.5k\u002Fvariant |\n| 10% | 15k\u002Fvariant | 3.8k\u002Fvariant | 690\u002Fvariant |\n\nPer variant, for 95% confidence (two-sided) and 80% power. Lift is relative (3% → 3.6% is a 20% lift).\n\n**Calculators:**\n- [Evan Miller's](https:\u002F\u002Fwww.evanmiller.org\u002Fab-testing\u002Fsample-size.html)\n- [Optimizely's](https:\u002F\u002Fwww.optimizely.com\u002Fsample-size-calculator\u002F)\n\n**For detailed sample size tables and duration calculations**: See [references\u002Fsample-size-guide.md](references\u002Fsample-size-guide.md)\n\n---\n\n## Metrics Selection\n\n### Primary Metric\n- Single metric that matters most\n- Directly tied to hypothesis\n- What you'll use to call the test\n\n### Secondary Metrics\n- Support primary metric interpretation\n- Explain why\u002Fhow the change worked\n\n### Guardrail Metrics\n- Things that shouldn't get worse\n- Stop test if significantly negative\n\n### Example: Pricing Page Test\n- **Primary**: Plan selection rate\n- **Secondary**: Time on page, plan distribution\n- **Guardrail**: Support tickets, refund rate\n\n### Opt-In Elements: Measure the Exposed Group\nWhen a change only reaches visitors who interact with it (a hero video, a calculator, a chat widget), a test on overall conversion is underpowered: if 10% of visitors click play, the other 90% add noise and no signal. Either run a triggered analysis (log the same trigger point in both arms, such as the play button coming into view, and compare only visitors who reached it; don't filter on clicks, since the variant can change who clicks), or skip the test, ship the better version, and compare versions on engagement (watch-through) and viewer conversion, tagged by version ID. The second is a directional comparison, not a controlled test.\n\n---\n\n## Designing Variants\n\n### What to Vary\n\n| Category | Examples |\n|----------|----------|\n| Headlines\u002FCopy | Message angle, value prop, specificity, tone |\n| Visual Design | Layout, color, images, hierarchy |\n| CTA | Button copy, size, placement, number |\n| Content | Information included, order, amount, social proof |\n\n### Best Practices\n- Single, meaningful change\n- Bold enough to make a difference\n- True to the hypothesis\n\n---\n\n## Traffic Allocation\n\n| Approach | Split | When to Use |\n|----------|-------|-------------|\n| Standard | 50\u002F50 | Default for A\u002FB |\n| Conservative | 90\u002F10, 80\u002F20 | Limit risk of bad variant |\n| Ramping | Start small, increase | Technical risk mitigation |\n\n**Considerations:**\n- Consistency: Users see same variant on return\n- Balanced exposure across time of day\u002Fweek\n\n---\n\n## Implementation\n\n### Client-Side\n- JavaScript modifies page after load\n- Quick to implement, can cause flicker\n- Tools: PostHog, Optimizely, VWO\n\n### Server-Side\n- Variant determined before render\n- No flicker, requires dev work\n- Tools: PostHog, LaunchDarkly, Split\n\n---\n\n## Running the Test\n\n### Pre-Launch Checklist\n- [ ] Hypothesis documented\n- [ ] Primary metric defined\n- [ ] Sample size calculated\n- [ ] Variants implemented correctly\n- [ ] Tracking verified\n- [ ] QA completed on all variants\n\n### During the Test\n\n**DO:**\n- Monitor for technical issues\n- Check segment quality\n- Document external factors\n\n**Avoid:**\n- Peek at results and stop early\n- Make changes to variants\n- Add traffic from new sources\n\n### The Peeking Problem\nLooking at results before reaching sample size and stopping early leads to false positives and wrong decisions. Pre-commit to sample size and trust the process.\n\n---\n\n## Analyzing Results\n\n### Statistical Significance\n- For a pre-specified fixed-horizon test, compare its p-value with the chosen significance level (commonly α = 0.05).\n- A p-value describes how incompatible the data are with the null model: the probability, **assuming that model and its assumptions**, of a result at least as extreme as the observed one. It is not the probability that the result is random, that the null is true, or that a variant will win again.\n- A 95% confidence interval comes from a procedure with 95% coverage over repeated samples under its assumptions. It is not a 95% posterior probability that this particular interval contains the true effect. Report the interval and effect size alongside the p-value.\n- Use the planned analysis and stopping rule. Sequential tests and Bayesian analyses have their own interpretation; do not translate every platform's “confidence” score into a fixed-horizon p-value.\n\nThese distinctions follow the [American Statistical Association's p-value statement](https:\u002F\u002Fwww.amstat.org\u002Fasa\u002Ffiles\u002Fpdfs\u002Fp-valuestatement.pdf). Statistical significance alone does not establish business value or justify shipping a variant.\n\n### Analysis Checklist\n\n1. **Reach sample size?** If not, result is preliminary\n2. **Statistically significant?** Check confidence intervals\n3. **Effect size meaningful?** Compare to MDE, project impact\n4. **Secondary metrics consistent?** Support the primary?\n5. **Guardrail concerns?** Anything get worse?\n6. **Segment differences?** Mobile vs. desktop? New vs. returning?\n\n### Interpreting Results\n\n| Result | Conclusion |\n|--------|------------|\n| Significant winner | Check effect size, uncertainty and guardrails before implementing |\n| Significant loser | Keep control, learn why |\n| No significant difference | Report the effect interval: it may still allow meaningful benefit and harm, or may exclude effects worth pursuing. Follow the planned stopping rule; do not extend a finished fixed-horizon test until it becomes significant. Plan a new test if needed. |\n| Mixed signals | Check data quality and planned metrics; label unplanned segment findings exploratory and confirm them in a new test |\n\n---\n\n## Documentation\n\nDocument every test with:\n- Hypothesis\n- Variants (with screenshots)\n- Results (sample, metrics, significance)\n- Decision and learnings\n\n**For templates**: See [references\u002Ftest-templates.md](references\u002Ftest-templates.md)\n\n---\n\n## Growth Experimentation Program\n\nIndividual tests are valuable. A continuous experimentation program is a compounding asset. This section covers how to run experiments as an ongoing growth engine, not just one-off tests.\n\n### The Experiment Loop\n\n```\n1. Generate hypotheses (from data, research, competitors, customer feedback)\n2. Prioritize with ICE scoring\n3. Design and run the test\n4. Analyze results with statistical rigor\n5. Promote winners to a playbook\n6. Generate new hypotheses from learnings\n→ Repeat\n```\n\n### Hypothesis Generation\n\nFeed your experiment backlog from multiple sources:\n\n| Source | What to Look For |\n|--------|-----------------|\n| Analytics | Drop-off points, low-converting pages, underperforming segments |\n| Customer research | Pain points, confusion, unmet expectations |\n| Competitor analysis | Features, messaging, or UX patterns they use that you don't |\n| Support tickets | Recurring questions or complaints about conversion flows |\n| Heatmaps\u002Frecordings | Where users hesitate, rage-click, or abandon |\n| Past experiments | \"Significant loser\" tests often reveal new angles to try |\n\n### ICE Prioritization\n\nScore each hypothesis 1-10 on three dimensions:\n\n| Dimension | Question |\n|-----------|----------|\n| **Impact** | If this works, how much will it move the primary metric? |\n| **Confidence** | How sure are we this will work? (Based on data, not gut.) |\n| **Ease** | How fast and cheap can we ship and measure this? |\n\n**ICE Score** = (Impact + Confidence + Ease) \u002F 3\n\nRun highest-scoring experiments first. Re-score monthly as context changes.\n\n### Experiment Velocity\n\nTrack your experimentation rate as a leading indicator of growth:\n\n| Metric | Target |\n|--------|--------|\n| Experiments launched per month | 4-8 for most teams |\n| Win rate | 20-30% is common for mature programs (sustained higher rates may indicate conservative hypotheses) |\n| Average test duration | 2-4 weeks |\n| Backlog depth | 20+ hypotheses queued |\n| Cumulative lift | Compound gains from all winners |\n\n### The Experiment Playbook\n\nWhen a test wins, don't just implement it — document the pattern:\n\n```\n## [Experiment Name]\n**Date**: [date]\n**Hypothesis**: [the hypothesis]\n**Sample size**: [n per variant]\n**Result**: [winner\u002Floser\u002Finconclusive] — [primary metric] changed by [X%] (95% CI: [range], p=[value])\n**Guardrails**: [any guardrail metrics and their outcomes]\n**Segment deltas**: [notable differences by device, segment, or cohort]\n**Why it worked\u002Ffailed**: [analysis]\n**Pattern**: [the reusable insight — e.g., \"social proof near pricing CTAs increases plan selection\"]\n**Apply to**: [other pages\u002Fflows where this pattern might work]\n**Status**: [implemented \u002F parked \u002F needs follow-up test]\n```\n\nOver time, your playbook becomes a library of proven growth patterns specific to your product and audience.\n\n### Experiment Cadence\n\n**Weekly (30 min)**: Review running experiments for technical issues and guardrail metrics. Don't call winners early — but do stop tests where guardrails are significantly negative.\n\n**Bi-weekly**: Conclude completed experiments. Analyze results, update playbook, launch next experiment from backlog.\n\n**Monthly (1 hour)**: Review experiment velocity, win rate, cumulative lift. Replenish hypothesis backlog. Re-prioritize with ICE.\n\n**Quarterly**: Audit the playbook. Which patterns have been applied broadly? Which winning patterns haven't been scaled yet? What areas of the funnel are under-tested?\n\n---\n\n## Common Mistakes\n\n### Test Design\n- Testing too small a change (undetectable)\n- Testing too many things (can't isolate)\n- No clear hypothesis\n\n### Execution\n- Stopping early\n- Changing things mid-test\n- Not checking implementation\n\n### Analysis\n- Ignoring confidence intervals\n- Cherry-picking segments\n- Over-interpreting inconclusive results\n\n---\n\n## Task-Specific Questions\n\n1. What's your current conversion rate?\n2. How much traffic does this page get?\n3. What change are you considering and why?\n4. What's the smallest improvement worth detecting?\n5. What tools do you have for testing?\n6. Have you tested this area before?\n\n---\n\n## Related Skills\n\n- **cro**: For generating test ideas based on CRO principles\n- **analytics**: For setting up test measurement\n- **copywriting**: For creating variant copy\n","# A\u002FB Test Setup\n\nYou are an expert in experimentation and A\u002FB testing. Your goal is to help design tests that produce statistically valid, actionable results.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore designing a test, understand:\n\n1. **Test Context** - What are you trying to improve? What change are you considering?\n2. **Current State** - Baseline conversion rate? Current traffic volume?\n3. **Constraints** - Technical complexity? Timeline? Tools available?\n\n---\n\n## Core Principles\n\n### 1. Start with a Hypothesis\n- Not just \"let's see what happens\"\n- Specific prediction of outcome\n- Based on reasoning or data\n\n### 2. Test One Thing\n- Single variable per test\n- Otherwise you don't know what worked\n\n### 3. Statistical Rigor\n- Pre-determine sample size\n- Don't peek and stop early\n- Commit to the methodology\n\n### 4. Measure What Matters\n- Primary metric tied to business value\n- Secondary metrics for context\n- Guardrail metrics to prevent harm\n\n---\n\n## Hypothesis Framework\n\n### Structure\n\n```\nBecause [observation\u002Fdata],\nwe believe [change]\nwill cause [expected outcome]\nfor [audience].\nWe'll know this is true when [metrics].\n```\n\n### Example\n\n**Weak**: \"Changing the button color might increase clicks.\"\n\n**Strong**: \"Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start.\"\n\n---\n\n## Test Types\n\n| Type | Description | Traffic Needed |\n|------|-------------|----------------|\n| A\u002FB | Two versions, single change | Moderate |\n| A\u002FB\u002Fn | Multiple variants | Higher |\n| MVT | Multiple changes in combinations | Very high |\n| Split URL | Different URLs for variants | Moderate |\n\n---\n\n## Sample Size\n\n### Quick Reference\n\n| Baseline | 10% Lift | 20% Lift | 50% Lift |\n|----------|----------|----------|----------|\n| 1% | 160k\u002Fvariant | 43k\u002Fvariant | 7.7k\u002Fvariant |\n| 3% | 53k\u002Fvariant | 14k\u002Fvariant | 2.5k\u002Fvariant |\n| 5% | 31k\u002Fvariant | 8.2k\u002Fvariant | 1.5k\u002Fvariant |\n| 10% | 15k\u002Fvariant | 3.8k\u002Fvariant | 690\u002Fvariant |\n\nPer variant, for 95% confidence (two-sided) and 80% power. Lift is relative (3% → 3.6% is a 20% lift).\n\n**Calculators:**\n- [Evan Miller's](https:\u002F\u002Fwww.evanmiller.org\u002Fab-testing\u002Fsample-size.html)\n- [Optimizely's](https:\u002F\u002Fwww.optimizely.com\u002Fsample-size-calculator\u002F)\n\n**For detailed sample size tables and duration calculations**: See [references\u002Fsample-size-guide.md](references\u002Fsample-size-guide.md)\n\n---\n\n## Metrics Selection\n\n### Primary Metric\n- Single metric that matters most\n- Directly tied to hypothesis\n- What you'll use to call the test\n\n### Secondary Metrics\n- Support primary metric interpretation\n- Explain why\u002Fhow the change worked\n\n### Guardrail Metrics\n- Things that shouldn't get worse\n- Stop test if significantly negative\n\n### Example: Pricing Page Test\n- **Primary**: Plan selection rate\n- **Secondary**: Time on page, plan distribution\n- **Guardrail**: Support tickets, refund rate\n\n### Opt-In Elements: Measure the Exposed Group\nWhen a change only reaches visitors who interact with it (a hero video, a calculator, a chat widget), a test on overall conversion is underpowered: if 10% of visitors click play, the other 90% add noise and no signal. Either run a triggered analysis (log the same trigger point in both arms, such as the play button coming into view, and compare only visitors who reached it; don't filter on clicks, since the variant can change who clicks), or skip the test, ship the better version, and compare versions on engagement (watch-through) and viewer conversion, tagged by version ID. The second is a directional comparison, not a controlled test.\n\n---\n\n## Designing Variants\n\n### What to Vary\n\n| Category | Examples |\n|----------|----------|\n| Headlines\u002FCopy | Message angle, value prop, specificity, tone |\n| Visual Design | Layout, color, images, hierarchy |\n| CTA | Button copy, size, placement, number |\n| Content | Information included, order, amount, social proof |\n\n### Best Practices\n- Single, meaningful change\n- Bold enough to make a difference\n- True to the hypothesis\n\n---\n\n## Traffic Allocation\n\n| Approach | Split | When to Use |\n|----------|-------|-------------|\n| Standard | 50\u002F50 | Default for A\u002FB |\n| Conservative | 90\u002F10, 80\u002F20 | Limit risk of bad variant |\n| Ramping | Start small, increase | Technical risk mitigation |\n\n**Considerations:**\n- Consistency: Users see same variant on return\n- Balanced exposure across time of day\u002Fweek\n\n---\n\n## Implementation\n\n### Client-Side\n- JavaScript modifies page after load\n- Quick to implement, can cause flicker\n- Tools: PostHog, Optimizely, VWO\n\n### Server-Side\n- Variant determined before render\n- No flicker, requires dev work\n- Tools: PostHog, LaunchDarkly, Split\n\n---\n\n## Running the Test\n\n### Pre-Launch Checklist\n- [ ] Hypothesis documented\n- [ ] Primary metric defined\n- [ ] Sample size calculated\n- [ ] Variants implemented correctly\n- [ ] Tracking verified\n- [ ] QA completed on all variants\n\n### During the Test\n\n**DO:**\n- Monitor for technical issues\n- Check segment quality\n- Document external factors\n\n**Avoid:**\n- Peek at results and stop early\n- Make changes to variants\n- Add traffic from new sources\n\n### The Peeking Problem\nLooking at results before reaching sample size and stopping early leads to false positives and wrong decisions. Pre-commit to sample size and trust the process.\n\n---\n\n## Analyzing Results\n\n### Statistical Significance\n- For a pre-specified fixed-horizon test, compare its p-value with the chosen significance level (commonly α = 0.05).\n- A p-value describes how incompatible the data are with the null model: the probability, **assuming that model and its assumptions**, of a result at least as extreme as the observed one. It is not the probability that the result is random, that the null is true, or that a variant will win again.\n- A 95% confidence interval comes from a procedure with 95% coverage over repeated samples under its assumptions. It is not a 95% posterior probability that this particular interval contains the true effect. Report the interval and effect size alongside the p-value.\n- Use the planned analysis and stopping rule. Sequential tests and Bayesian analyses have their own interpretation; do not translate every platform's “confidence” score into a fixed-horizon p-value.\n\nThese distinctions follow the [American Statistical Association's p-value statement](https:\u002F\u002Fwww.amstat.org\u002Fasa\u002Ffiles\u002Fpdfs\u002Fp-valuestatement.pdf). Statistical significance alone does not establish business value or justify shipping a variant.\n\n### Analysis Checklist\n\n1. **Reach sample size?** If not, result is preliminary\n2. **Statistically significant?** Check confidence intervals\n3. **Effect size meaningful?** Compare to MDE, project impact\n4. **Secondary metrics consistent?** Support the primary?\n5. **Guardrail concerns?** Anything get worse?\n6. **Segment differences?** Mobile vs. desktop? New vs. returning?\n\n### Interpreting Results\n\n| Result | Conclusion |\n|--------|------------|\n| Significant winner | Check effect size, uncertainty and guardrails before implementing |\n| Significant loser | Keep control, learn why |\n| No significant difference | Report the effect interval: it may still allow meaningful benefit and harm, or may exclude effects worth pursuing. Follow the planned stopping rule; do not extend a finished fixed-horizon test until it becomes significant. Plan a new test if needed. |\n| Mixed signals | Check data quality and planned metrics; label unplanned segment findings exploratory and confirm them in a new test |\n\n---\n\n## Documentation\n\nDocument every test with:\n- Hypothesis\n- Variants (with screenshots)\n- Results (sample, metrics, significance)\n- Decision and learnings\n\n**For templates**: See [references\u002Ftest-templates.md](references\u002Ftest-templates.md)\n\n---\n\n## Growth Experimentation Program\n\nIndividual tests are valuable. A continuous experimentation program is a compounding asset. This section covers how to run experiments as an ongoing growth engine, not just one-off tests.\n\n### The Experiment Loop\n\n```\n1. Generate hypotheses (from data, research, competitors, customer feedback)\n2. Prioritize with ICE scoring\n3. Design and run the test\n4. Analyze results with statistical rigor\n5. Promote winners to a playbook\n6. Generate new hypotheses from learnings\n→ Repeat\n```\n\n### Hypothesis Generation\n\nFeed your experiment backlog from multiple sources:\n\n| Source | What to Look For |\n|--------|-----------------|\n| Analytics | Drop-off points, low-converting pages, underperforming segments |\n| Customer research | Pain points, confusion, unmet expectations |\n| Competitor analysis | Features, messaging, or UX patterns they use that you don't |\n| Support tickets | Recurring questions or complaints about conversion flows |\n| Heatmaps\u002Frecordings | Where users hesitate, rage-click, or abandon |\n| Past experiments | \"Significant loser\" tests often reveal new angles to try |\n\n### ICE Prioritization\n\nScore each hypothesis 1-10 on three dimensions:\n\n| Dimension | Question |\n|-----------|----------|\n| **Impact** | If this works, how much will it move the primary metric? |\n| **Confidence** | How sure are we this will work? (Based on data, not gut.) |\n| **Ease** | How fast and cheap can we ship and measure this? |\n\n**ICE Score** = (Impact + Confidence + Ease) \u002F 3\n\nRun highest-scoring experiments first. Re-score monthly as context changes.\n\n### Experiment Velocity\n\nTrack your experimentation rate as a leading indicator of growth:\n\n| Metric | Target |\n|--------|--------|\n| Experiments launched per month | 4-8 for most teams |\n| Win rate | 20-30% is common for mature programs (sustained higher rates may indicate conservative hypotheses) |\n| Average test duration | 2-4 weeks |\n| Backlog depth | 20+ hypotheses queued |\n| Cumulative lift | Compound gains from all winners |\n\n### The Experiment Playbook\n\nWhen a test wins, don't just implement it — document the pattern:\n\n```\n## [Experiment Name]\n**Date**: [date]\n**Hypothesis**: [the hypothesis]\n**Sample size**: [n per variant]\n**Result**: [winner\u002Floser\u002Finconclusive] — [primary metric] changed by [X%] (95% CI: [range], p=[value])\n**Guardrails**: [any guardrail metrics and their outcomes]\n**Segment deltas**: [notable differences by device, segment, or cohort]\n**Why it worked\u002Ffailed**: [analysis]\n**Pattern**: [the reusable insight — e.g., \"social proof near pricing CTAs increases plan selection\"]\n**Apply to**: [other pages\u002Fflows where this pattern might work]\n**Status**: [implemented \u002F parked \u002F needs follow-up test]\n```\n\nOver time, your playbook becomes a library of proven growth patterns specific to your product and audience.\n\n### Experiment Cadence\n\n**Weekly (30 min)**: Review running experiments for technical issues and guardrail metrics. Don't call winners early — but do stop tests where guardrails are significantly negative.\n\n**Bi-weekly**: Conclude completed experiments. Analyze results, update playbook, launch next experiment from backlog.\n\n**Monthly (1 hour)**: Review experiment velocity, win rate, cumulative lift. Replenish hypothesis backlog. Re-prioritize with ICE.\n\n**Quarterly**: Audit the playbook. Which patterns have been applied broadly? Which winning patterns haven't been scaled yet? What areas of the funnel are under-tested?\n\n---\n\n## Common Mistakes\n\n### Test Design\n- Testing too small a change (undetectable)\n- Testing too many things (can't isolate)\n- No clear hypothesis\n\n### Execution\n- Stopping early\n- Changing things mid-test\n- Not checking implementation\n\n### Analysis\n- Ignoring confidence intervals\n- Cherry-picking segments\n- Over-interpreting inconclusive results\n\n---\n\n## Task-Specific Questions\n\n1. What's your current conversion rate?\n2. How much traffic does this page get?\n3. What change are you considering and why?\n4. What's the smallest improvement worth detecting?\n5. What tools do you have for testing?\n6. Have you tested this area before?\n\n---\n\n## Related Skills\n\n- **cro**: For generating test ideas based on CRO principles\n- **analytics**: For setting up test measurement\n- **copywriting**: For creating variant copy\n",{"name":5,"metadata":24,"description":7},{"version":25},"2.0.7","main","915ddb053d843c5ce27850e183ef389a23af0865","skills\u002Fab-testing",0,"https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills","https:\u002F\u002Fgithub.com\u002FSanHsien","Personal & open-source projects · local-first tools · verifiable AI workflows · Windows-first software","2026-11-10 08:49:08",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SanHsien\u002Fagent-marketing-skills --skill ab-testing",{"tool":40,"command":41},"bunx","bunx skills add SanHsien\u002Fagent-marketing-skills --skill ab-testing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SanHsien\u002Fagent-marketing-skills --skill ab-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fab-testing\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",9025,"https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fab-testing\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fsample-size-guide.md",9183,"https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fab-testing\u002Freferences\u002Fsample-size-guide.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ftest-templates.md",6473,"https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fab-testing\u002Freferences\u002Ftest-templates.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7BHS0KS1MG379JY58DAZBFK","video","When the user wants to create video with AI tools or code, or asks which approach to use (screen recording, AI avatar, generated, or templated) or how to make videos repeatably: product demos, AI generation (Veo, Sora, HeyGen), programmatic video with Remotion. For what to post, see social. For video ads, see ad-creative.","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7BHRSBECVDC5Q7R89DKD39P","social","When the user wants organic social content for LinkedIn, X, Instagram, TikTok, or Facebook, or asks what to post, which format to favor, or from which account: posts, threads, carousels, short-form video scripts, calendars, build-in-public posts from commits, listening. No AI tells like 'it's not X, it's Y' or broetry. For content strategy, see content-strategy. For paid ads, see ad-creative. For press, see public-relations.","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7BHRK1XYT9GADBH88PW1BWS","sms","When the user wants SMS, MMS, or WhatsApp marketing, or asks whether texting is worth it or a message is allowed: abandoned cart, win-back, and promo texts, WhatsApp templates and windows, TCPA and A2P 10DLC compliance, SMS vs email. For email, see emails. For phone capture popups, see popups.","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7BHRDPPT9EMQCF3K4GT4JS5","site-architecture","When the user wants to plan or restructure a website, or asks which pages they need or where something belongs: hierarchy, navigation, URL structure, internal linking, website builders and migrations. Not XML sitemaps (see seo-audit). For structured data, see schema.","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7BHR7C7WCK19QPG37H5H4D8","signup","When the user wants better signup, registration, and trial start flows, or asks which fields or steps to cut or whether to require a card: SSO and drop-off before an account exists. For what happens after signup, see onboarding. For lead forms that don't create an account, see cro.","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7BHQZSQ846P3A97R4CNEQ9Z","seo-audit","When the user wants to audit or diagnose SEO, or asks why traffic dropped, a page won't rank, or whether a setup like canonicals, hreflang, or redirects is right: technical SEO, indexing, Google updates, on-page and titles, Core Web Vitals, local SEO. Start here when someone just says their SEO is bad. For pages at scale, see programmatic-seo. For structured data, see schema. For AI search, see ai-seo.","https:\u002F\u002Fgithub.com\u002FSanHsien\u002Fagent-marketing-skills\u002Fblob\u002Fmain\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]