|
| 1 | +{ |
| 2 | + "skill_name": "ab-test-setup", |
| 3 | + "evals": [ |
| 4 | + { |
| 5 | + "id": 1, |
| 6 | + "prompt": "I want to A/B test our homepage headline. We currently say 'The All-in-One Project Management Tool' and want to test something benefit-focused. We get about 15,000 visitors/month and our current signup rate is 3.2%.", |
| 7 | + "expected_output": "Should check for product-marketing-context.md first. Should build a proper hypothesis using the framework: 'Because [observation], we believe [change] will cause [outcome], which we'll measure by [metric].' Should identify this as an A/B test (two variants). Should calculate or reference sample size needs based on 15,000 monthly visitors and 3.2% baseline. Should define primary metric (signup rate), secondary metrics, and guardrail metrics. Should warn about the peeking problem and recommend a fixed test duration. Should provide the test plan in the structured output format.", |
| 8 | + "assertions": [ |
| 9 | + "Checks for product-marketing-context.md", |
| 10 | + "Uses the hypothesis framework with observation, belief, outcome, and metric", |
| 11 | + "Identifies as A/B test type", |
| 12 | + "Addresses sample size calculation based on traffic and baseline rate", |
| 13 | + "Defines primary metric (signup rate)", |
| 14 | + "Defines secondary and guardrail metrics", |
| 15 | + "Warns about the peeking problem", |
| 16 | + "Provides structured test plan output" |
| 17 | + ], |
| 18 | + "files": [] |
| 19 | + }, |
| 20 | + { |
| 21 | + "id": 2, |
| 22 | + "prompt": "we want to test like 4 different CTA button colors on our pricing page. is that a good idea?", |
| 23 | + "expected_output": "Should trigger on casual phrasing. Should identify this as an A/B/n test (multiple variants). Should caution that testing 4 variants requires significantly more traffic than a simple A/B test. Should reference the sample size quick reference showing traffic multipliers for multiple variants. Should question whether button color alone is likely to produce meaningful lift vs testing CTA copy, placement, or surrounding context. Should recommend either reducing to 2 variants or ensuring sufficient traffic. Should still provide hypothesis framework and test setup if proceeding.", |
| 24 | + "assertions": [ |
| 25 | + "Triggers on casual phrasing", |
| 26 | + "Identifies as A/B/n test (multiple variants)", |
| 27 | + "Cautions about increased traffic needs for 4 variants", |
| 28 | + "References sample size requirements", |
| 29 | + "Questions whether button color alone is high-impact", |
| 30 | + "Suggests alternative higher-impact elements to test", |
| 31 | + "Provides hypothesis framework" |
| 32 | + ], |
| 33 | + "files": [] |
| 34 | + }, |
| 35 | + { |
| 36 | + "id": 3, |
| 37 | + "prompt": "Our test has been running for 3 days and Variant B is winning with 95% confidence. Should we call it?", |
| 38 | + "expected_output": "Should immediately address the peeking problem. Should explain that checking results early inflates false positive rates. Should recommend running for the full pre-calculated duration regardless of early results. Should explain why early significance can be misleading (regression to the mean, day-of-week effects, audience mix shifts). Should provide guidance on when it IS appropriate to stop early (sequential testing methods). Should recommend the pre-test commitment to duration.", |
| 39 | + "assertions": [ |
| 40 | + "Addresses the peeking problem directly", |
| 41 | + "Explains why early significance is misleading", |
| 42 | + "Recommends running for full pre-calculated duration", |
| 43 | + "Mentions day-of-week effects or audience mix shifts", |
| 44 | + "Explains false positive rate inflation from peeking", |
| 45 | + "Mentions sequential testing as alternative approach" |
| 46 | + ], |
| 47 | + "files": [] |
| 48 | + }, |
| 49 | + { |
| 50 | + "id": 4, |
| 51 | + "prompt": "Help me set up a multivariate test on our landing page. I want to test the headline, hero image, and CTA button simultaneously.", |
| 52 | + "expected_output": "Should identify this as a Multivariate Test (MVT). Should explain that MVT tests combinations of elements and requires much more traffic than A/B tests. Should calculate or reference traffic needs (combinations multiply: e.g., 2 headlines × 2 images × 2 CTAs = 8 combinations). Should recommend MVT only if traffic supports it, otherwise suggest sequential A/B tests. Should build hypotheses for each element being tested. Should define interaction effects to watch for. Should provide structured test plan.", |
| 53 | + "assertions": [ |
| 54 | + "Identifies as multivariate test (MVT)", |
| 55 | + "Explains MVT tests combinations of elements", |
| 56 | + "Addresses dramatically higher traffic requirements", |
| 57 | + "Calculates number of combinations", |
| 58 | + "Suggests sequential A/B tests as alternative if traffic insufficient", |
| 59 | + "Builds hypotheses for each element", |
| 60 | + "Provides structured test plan" |
| 61 | + ], |
| 62 | + "files": [] |
| 63 | + }, |
| 64 | + { |
| 65 | + "id": 5, |
| 66 | + "prompt": "What metrics should I track for an A/B test on our trial signup page? We're testing a longer form (adds company size and role fields) against the current short form.", |
| 67 | + "expected_output": "Should apply the metrics selection framework with three tiers: primary, secondary, and guardrail metrics. Primary: form completion rate (the direct conversion metric). Secondary: lead quality metrics (SQL conversion rate, activation rate post-signup). Guardrail: overall signup volume (ensure longer form doesn't tank total signups below acceptable threshold). Should explain the tradeoff between conversion quantity and lead quality. Should note that this test needs longer observation window to measure downstream metrics.", |
| 68 | + "assertions": [ |
| 69 | + "Applies three-tier metric framework (primary, secondary, guardrail)", |
| 70 | + "Identifies form completion rate as primary metric", |
| 71 | + "Identifies lead quality as secondary metric", |
| 72 | + "Defines guardrail metrics to protect against negative outcomes", |
| 73 | + "Explains quantity vs quality tradeoff", |
| 74 | + "Notes need for longer observation window for downstream metrics" |
| 75 | + ], |
| 76 | + "files": [] |
| 77 | + }, |
| 78 | + { |
| 79 | + "id": 6, |
| 80 | + "prompt": "Can you help me write copy for our new landing page? We want to test it against the current version.", |
| 81 | + "expected_output": "Should recognize this is primarily a copywriting task, not a test setup task. Should defer to or cross-reference the copywriting skill for writing the actual copy. May help frame the test hypothesis and setup, but should make clear that copywriting is the right skill for creating the page copy itself.", |
| 82 | + "assertions": [ |
| 83 | + "Recognizes this as primarily a copywriting task", |
| 84 | + "References or defers to copywriting skill", |
| 85 | + "Does not attempt to write full page copy using test setup patterns", |
| 86 | + "May offer to help with test hypothesis and setup" |
| 87 | + ], |
| 88 | + "files": [] |
| 89 | + }, |
| 90 | + { |
| 91 | + "id": 7, |
| 92 | + "prompt": "We ran an A/B test on our pricing page for 4 weeks. Control: 2.1% conversion. Variant: 2.4% conversion. 12,000 visitors per variant. Is this statistically significant? Should we ship it?", |
| 93 | + "expected_output": "Should evaluate the results against statistical significance criteria. Should calculate or estimate whether the sample size is sufficient to detect a 0.3 percentage point lift from a 2.1% baseline (this is a ~14% relative lift). Should reference the 95% confidence threshold. Should discuss practical significance vs statistical significance. Should recommend whether to ship, continue testing, or iterate. Should consider segment analysis if results are borderline.", |
| 94 | + "assertions": [ |
| 95 | + "Evaluates against statistical significance criteria", |
| 96 | + "Addresses whether sample size is sufficient for this effect size", |
| 97 | + "References 95% confidence threshold", |
| 98 | + "Distinguishes statistical significance from practical significance", |
| 99 | + "Provides clear recommendation on shipping", |
| 100 | + "Suggests segment analysis or follow-up if borderline" |
| 101 | + ], |
| 102 | + "files": [] |
| 103 | + } |
| 104 | + ] |
| 105 | +} |
0 commit comments