statistical-analyst

Run hypothesis tests, calculate sample sizes, and interpret A/B experiment results with effect sizes.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill statistical-analyst-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: statistical-analyst
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/statistical-analyst
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill statistical-analyst-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Teams often misread experiment data — shipping on noise, killing real winners, or launching underpowered tests. This Skill turns raw experiment numbers into statistically grounded decisions by running the correct hypothesis test, computing effect sizes, and flagging validity threats like peeking and multiple comparisons. ## Core Features & Use Cases - Hypothesis Testing: Run two-proportion Z-tests, Welch's t-tests, and Chi-square tests with p-values, confidence intervals, and effect sizes (Cohen's d/h, Cramér's V) via pure-stdlib Python scripts. - Pre-Launch Sample Sizing: Calculate required sample size per variant from baseline rate, MDE, alpha, and power, with duration estimates and power/MDE tradeoff tables. - Confidence Intervals: Compute Wilson score intervals for proportions and z-based intervals for means with plain-English interpretation. - Use Case: Your A/B test shows 5.0% vs 6.2% conversion on 5,000 users per variant. The Skill runs a Z-test, reports p=0.008 with Cohen's h=0.054, and warns the effect is negligible despite significance — recommending you hold rather than ship. ## Quick Start Ask the assistant to analyze your A/B test results by providing control and treatment sample sizes and conversion counts, and it will return a significance verdict with effect size and a ship-or-hold recommendation.

Frequently Asked Questions about statistical-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test if my A/B test result is statistically significant?▼

Run a two-proportion Z-test for conversion rates or Welch's t-test for continuous metrics using the hypothesis tester script with your control and treatment sample sizes and observed values. It returns the p-value, confidence interval, effect size, and a plain-English verdict on whether to ship.

How do I calculate sample size for an A/B test before launch?▼

Use the sample size calculator with your baseline conversion rate, minimum detectable effect as a relative change, significance level, and desired power. It returns the required n per variant, total sample, and a duration estimate if you provide daily traffic.

What is the difference between statistical and practical significance?▼

Statistical significance (p < alpha) means the difference is unlikely due to chance, while practical significance depends on effect size. A result can be significant with a negligible Cohen's h or d, meaning the business impact is too small to justify shipping.

Does this require scipy or numpy for statistical tests?▼

No, all scripts use only the Python standard library math module. Normal, t, and chi-square distributions are computed via erfc, continued fractions, and series expansions, so no external packages need installation.

When should I not use a standard Z-test or t-test?▼

Avoid them with fewer than 30 samples per group without normality checks, heavy-tailed metrics like revenue with outliers, sequential peeking scenarios, or clustered data where observations are not independent. Use sequential testing, non-parametric methods, or cluster randomization instead.

Why does checking experiment results early inflate false positives?▼

Peeking before the planned end date inflates the effective alpha — checking at 50%, 75%, and 100% of planned n raises the true false positive rate from 5% to roughly 13%. Pre-commit to a stopping rule or use sequential testing methods like SPRT.