[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1V2ST7FA2MYQTR30PW7S6":3,"skill-same:01M6C1V2ST7FA2MYQTR30PW7S6":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6C1V2ST7FA2MYQTR30PW7S6","ab-test-setup",null,"When the user wants to plan, design, or implement an A\u002FB test or experiment. Also use when the user mentions \"A\u002FB test,\" \"split test,\" \"experiment,\" \"test this change,\" \"variant copy,\" \"multivariate test,\" \"hypothesis,\" \"conversion experiment,\" \"statistical significance,\" or \"test this.\" For tracking implementation, see analytics-tracking.","mne20114-hash\u002Fgest35bi","mne20114-hash","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224168109?v=4","01M6C0JCR7334CZ39YWTZXX2NG","01M6C0JCWN0NBWMQTW1CPG2Z4G",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fab-test-setup\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",[26,27,28,29,30,31,32,33,34,35,36,37,38],"test","setup","ab test setup","design","implement","change","analytics","hypothesis","plan","marketing","tracking","user","use","2026-11-10 10:12:30",false,"---\nname: \"ab-test-setup\"\ndescription: When the user wants to plan, design, or implement an A\u002FB test or experiment. Also use when the user mentions \"A\u002FB test,\" \"split test,\" \"experiment,\" \"test this change,\" \"variant copy,\" \"multivariate test,\" \"hypothesis,\" \"conversion experiment,\" \"statistical significance,\" or \"test this.\" For tracking implementation, see analytics-tracking.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\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 `.claude\u002Fproduct-marketing-context.md` exists, 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### Calculate It (bundled tool)\n\nUse this skill's own calculator — don't eyeball it:\n\n```bash\npython3 scripts\u002Fsample_size_calculator.py --baseline 0.05 --mde 0.20            # human-readable\npython3 scripts\u002Fsample_size_calculator.py --baseline 0.05 --mde 0.20 --json    # for pipelines\npython3 scripts\u002Fsample_size_calculator.py --baseline 0.05 --mde 0.20 --daily-traffic 2000  # adds test-duration estimate\n```\n\nPaste `sample_size_per_variation` and the duration estimate directly into the test plan's \"Sample size + duration\" row before any test is approved to run.\n\n### Quick Reference\n\nGenerated by `sample_size_calculator.py` (two-proportion z-test, α=0.05 two-tailed, 80% power; relative MDE):\n\n| Baseline | 10% Lift | 20% Lift | 50% Lift |\n|----------|----------|----------|----------|\n| 1% | 163k\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 | 683\u002Fvariant |\n\n**Cross-check calculators** (should agree with the script within rounding):\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---\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**DON'T:**\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- 95% confidence = p-value \u003C 0.05\n- Means \u003C5% chance result is random\n- Not a guarantee—just a threshold\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 | Implement variant |\n| Significant loser | Keep control, learn why |\n| No significant difference | Need more traffic or bolder test |\n| Mixed signals | Dig deeper, maybe segment |\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## 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## Proactive Triggers\n\nProactively offer A\u002FB test design when:\n\n1. **Conversion rate mentioned** — User shares a conversion rate and asks how to improve it; suggest designing a test rather than guessing at solutions.\n2. **Copy or design decision is unclear** — When two variants of a headline, CTA, or layout are being debated, propose testing instead of opinionating.\n3. **Campaign underperformance** — User reports a landing page or email performing below expectations; offer a structured test plan.\n4. **Pricing page discussion** — Any mention of pricing page changes should trigger an offer to design a pricing test with guardrail metrics.\n5. **Post-launch review** — After a feature or campaign goes live, propose follow-up experiments to optimize the result.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Experiment Brief | Markdown doc | Hypothesis, variants, metrics, sample size, duration, owner |\n| Sample Size Calculator Input | Table | Baseline rate, MDE, confidence level, power |\n| Pre-Launch QA Checklist | Checklist | Implementation, tracking, variant rendering verification |\n| Results Analysis Report | Markdown doc | Statistical significance, effect size, segment breakdown, decision |\n| Test Backlog | Prioritized list | Ranked experiments by expected impact and feasibility |\n\n---\n\n## Communication\n\nAll outputs should meet the quality standard: clear hypothesis, pre-registered metrics, and documented decisions. Avoid presenting inconclusive results as wins. Every test should produce a learning, even if the variant loses. Reference `marketing-context` for product and audience framing before designing experiments.\n\n---\n\n## Related Skills\n\n- **page-cro** — USE when you need ideas for *what* to test; NOT when you already have a hypothesis and just need test design.\n- **analytics-tracking** — USE to set up measurement infrastructure before running tests; NOT as a substitute for defining primary metrics upfront.\n- **campaign-analytics** — USE after tests conclude to fold results into broader campaign attribution; NOT during the test itself.\n- **pricing-strategy** — USE when test results affect pricing decisions; NOT to replace a controlled test with pure strategic reasoning.\n- **marketing-context** — USE as foundation before any test design to ensure hypotheses align with ICP and positioning; always load first.\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 `.claude\u002Fproduct-marketing-context.md` exists, 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### Calculate It (bundled tool)\n\nUse this skill's own calculator — don't eyeball it:\n\n```bash\npython3 scripts\u002Fsample_size_calculator.py --baseline 0.05 --mde 0.20            # human-readable\npython3 scripts\u002Fsample_size_calculator.py --baseline 0.05 --mde 0.20 --json    # for pipelines\npython3 scripts\u002Fsample_size_calculator.py --baseline 0.05 --mde 0.20 --daily-traffic 2000  # adds test-duration estimate\n```\n\nPaste `sample_size_per_variation` and the duration estimate directly into the test plan's \"Sample size + duration\" row before any test is approved to run.\n\n### Quick Reference\n\nGenerated by `sample_size_calculator.py` (two-proportion z-test, α=0.05 two-tailed, 80% power; relative MDE):\n\n| Baseline | 10% Lift | 20% Lift | 50% Lift |\n|----------|----------|----------|----------|\n| 1% | 163k\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 | 683\u002Fvariant |\n\n**Cross-check calculators** (should agree with the script within rounding):\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---\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**DON'T:**\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- 95% confidence = p-value \u003C 0.05\n- Means \u003C5% chance result is random\n- Not a guarantee—just a threshold\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 | Implement variant |\n| Significant loser | Keep control, learn why |\n| No significant difference | Need more traffic or bolder test |\n| Mixed signals | Dig deeper, maybe segment |\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## 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## Proactive Triggers\n\nProactively offer A\u002FB test design when:\n\n1. **Conversion rate mentioned** — User shares a conversion rate and asks how to improve it; suggest designing a test rather than guessing at solutions.\n2. **Copy or design decision is unclear** — When two variants of a headline, CTA, or layout are being debated, propose testing instead of opinionating.\n3. **Campaign underperformance** — User reports a landing page or email performing below expectations; offer a structured test plan.\n4. **Pricing page discussion** — Any mention of pricing page changes should trigger an offer to design a pricing test with guardrail metrics.\n5. **Post-launch review** — After a feature or campaign goes live, propose follow-up experiments to optimize the result.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Experiment Brief | Markdown doc | Hypothesis, variants, metrics, sample size, duration, owner |\n| Sample Size Calculator Input | Table | Baseline rate, MDE, confidence level, power |\n| Pre-Launch QA Checklist | Checklist | Implementation, tracking, variant rendering verification |\n| Results Analysis Report | Markdown doc | Statistical significance, effect size, segment breakdown, decision |\n| Test Backlog | Prioritized list | Ranked experiments by expected impact and feasibility |\n\n---\n\n## Communication\n\nAll outputs should meet the quality standard: clear hypothesis, pre-registered metrics, and documented decisions. Avoid presenting inconclusive results as wins. Every test should produce a learning, even if the variant loses. Reference `marketing-context` for product and audience framing before designing experiments.\n\n---\n\n## Related Skills\n\n- **page-cro** — USE when you need ideas for *what* to test; NOT when you already have a hypothesis and just need test design.\n- **analytics-tracking** — USE to set up measurement infrastructure before running tests; NOT as a substitute for defining primary metrics upfront.\n- **campaign-analytics** — USE after tests conclude to fold results into broader campaign attribution; NOT during the test itself.\n- **pricing-strategy** — USE when test results affect pricing decisions; NOT to replace a controlled test with pure strategic reasoning.\n- **marketing-context** — USE as foundation before any test design to ensure hypotheses align with ICP and positioning; always load first.\n",{"name":5,"license":14,"metadata":44,"description":7},{"author":45,"updated":46,"version":47,"category":35},"Alireza Rezvani",1772755200000,"1.0.0","main","510dd2917e051cc953dc55f56fd6ef442aa01b38","claude-skills\u002Fmarketing-skill\u002Fskills\u002Fab-test-setup","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi","https:\u002F\u002Fgithub.com\u002Fmne20114-hash","2026-10-28 07:50:31",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add mne20114-hash\u002Fgest35bi --skill ab-test-setup",{"tool":60,"command":61},"bunx","bunx skills add mne20114-hash\u002Fgest35bi --skill ab-test-setup",{"tool":63,"command":64},"pnpm","pnpm dlx skills add mne20114-hash\u002Fgest35bi --skill ab-test-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fab-test-setup\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fsample-size-guide.md","REFERENCE","参考文档",7068,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fab-test-setup\u002Freferences\u002Fsample-size-guide.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Ftest-templates.md",6250,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fab-test-setup\u002Freferences\u002Ftest-templates.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fsample_size_calculator.py","SCRIPT","脚本",12607,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fab-test-setup\u002Fscripts\u002Fsample_size_calculator.py",[85,121,142,165,190,209],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":102,"publishedAt":39},"01M6C27N3H0F9RGG2KASPASH04","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[91,94,97],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[87,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,38,120],"docx","pr","create","intake","search","audit","integrity","checkpoint","learning","js","format","direct","Rules","find","consensus","list","extract","outcomes",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":131,"publishedAt":39},"01M6C27DMGZ4D6ERNHSVA8H8RJ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},[123,132,133,104,134,106,108,135,136,109,137,138,139,140,114,115,141,116,37,38],"research","web","sentiment analysis","sentiment","Citations","analysis","discovery","open","tool","twitter",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":153,"publishedAt":39},"01M6C279M59X635VPD6Y9R616J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[148,149,150],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":151,"categoryName":152,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000037","律师与法务",[144,103,104,154,155,156,106,107,108,137,157,158,159,115,160,161,162,163,38,164],"competitive landscape","routing","product","commits","Word","text","acquisition","decisions","strategy","coverage","advice",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":39},"01M6C275RZWNRB3CCB14QQM7ES","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[171,174],{"categoryNo":172,"categoryName":173,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},[167,176,177,132,178,179,180,181,182,183,184,185,139,159,114,186,187,188,189,38],"google","browser automation","automation","generate","browser","fast","SET","doc","Video","Audio","check","ask","environment","overview",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":39},"01M6C2717B0QDJ3Y4PJP77BMW5","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[196,197,198,199],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":128,"categoryName":129,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[192,103,201,202,203,104,106,107,204,205,206,110,34,158,207,115,117,208,163,38],"MCP","writing","review","lane","keyless","literature review","researcher","question",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":219,"publishedAt":39},"01M6C26X5G3WDVWQ40Y16ZS19F","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[215,216,217,218],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":128,"categoryName":129,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[211,103,132,104,220,106,107,108,221,222,109,137,158,115,116,117,162,188,38,223],"help","data","Budget","innovation"]