PremiumEmail Triage Automation
- Read full threads
- Sort into 3 buckets
- Draft in your voice
- Approve & send
← All skills · Automation · A/B Test Planner

Premium
Premium
Free
PremiumAn example of what this Skill produces. Sample content, shown for illustration.
A/B Test Plan — sample Metric: Signup start rate | Baseline: 5% | MDE: +20% relative (+1.00 pp) | Arms: 2 (Control + 1 variant) | Confidence: 95% | Power: 80% Sample size: 8,160 per variant | 16,320 total | About 9 days at 2,000 visitors/day (50/50 split) Decision rule (pre-registered): call the test only when the smallest arm reaches 8,160 visitors; a variant wins only if it beats control by at least 1.00 pp and the difference is significant at 95% confidence. A significant result smaller than the MDE is real but too small to ship on this hypothesis. An inconclusive result is not a reason to extend the test — plan a new one. Sample sizes are planning estimates from the normal approximation at the stated confidence and power — not a guarantee, and this script does not analyse results.
We want to test moving the signup CTA above the fold on the BeanLoop pricing page — plan the test before we run it.Read https://skillu.dev/install/agent.md, then install the A/B Test Planner skill (ab-test-planner)./ab-test-planner, and describe what you want in plain words.No. It means every part of the plan is present and the input had no errors — the plan is complete, not the result. Most tests lose or tie; a plan that says so plainly is doing its job.
Because a small relative lift is a small absolute difference — 20% on a 5% baseline is only 1 percentage point, and telling 5% from 6% reliably takes about 8,160 visitors per variant. Halve the MDE and the sample roughly quadruples.