Prevent stakeholders from calling experiments too early
Generates automated A/B test reports with required sample sizes, current statistical significance, confidence intervals, and a clear "keep running" or "ready to call" recommendation. Stops premature peeking from killing valid experiments.
Create a skill called "Experiment Referee". For each A/B test I configure: (1) Before launch: Calculate required sample size given the primary metric, baseline conversion rate, minimum detectable effect, and desired power (default 80%). (2) During the test: Generate periodic reports showing current sample sizes per variant, observed effect size, p-value, confidence interval, and a clear verdict: "NOT SIGNIFICANT — keep running (estimated X days remaining)" or "SIGNIFICANT — ready to call." (3) For segment analysis: Apply Bonferroni or Benjamini-Hochberg correction for multiple comparisons and warn when segments are underpowered. (4) Include a non-technical summary for stakeholders that explains the conclusion without statistical jargon. (5) Alert me when an experiment reaches significance. Never recommend stopping a test before it reaches the pre-calculated sample size unless using a valid sequential testing framework.
Product managers peek at A/B test results on day 2 and want to ship the
"winning" variant. But it's not significant yet — the p-value is 0.3 and
the sample size is 20% of what's needed. This skill generates experiment
reports that make the statistical guardrails impossible to ignore.
Monday morning reports that write themselves
Automates the entire weekly/monthly reporting pipeline — runs the queries, populates the template, generates a narrative summary, flags anomalies, and emails/Slacks the finished report. You review it instead of building it.
Auto-explain what likely moved your metrics this week
Feeds on your KPI data and writes the narrative your stakeholders need — what changed, which segments likely drove it, and which movements look unusual. Turns numbers into a review-ready draft instead of a blank page.
Stop being the family project manager
Build a weekly schedule, decision rules, and scripts that prevent one parent from becoming the household operations manager. Coverage grid, handoff protocol, and conflict-prevention rules included.
From isolated to connected in 30 days
Motherhood is lonely by default. This recipe builds a 30-day plan to create repeatable, low-effort social connection — with scripts for invites, follow-ups, and a backup plan for introverts.