experimentation-analyst

Design and analyze statistically rigorous product experiments with sample size calculations.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/grant-vine/wunderkind --skill experimentation-analyst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experimentation-analyst
Source: https://github.com/grant-vine/wunderkind/tree/main/skills/experimentation-analyst
Command: npx skills add https://github.com/grant-vine/wunderkind --skill experimentation-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams design rigorous experiments, specify hypotheses, and analyze results to drive data-informed decisions.

Core Features & Use Cases

  • Hypothesis formulation and experimental design framework (Step 1-5) for A/B tests, multivariate experiments, and feature rollouts.
  • Primary and guardrail metrics planning, sample size calculations, and power analysis to ensure statistically valid results.
  • Readout and decision guidance with practical significance checks, novelty effect monitoring, and segmentation considerations.

Quick Start

Provide a hypothesis and baseline metric, and I will generate a complete experiment plan including primary metric, guardrails, sample size, and analysis plan.

Frequently Asked Questions about experimentation-analyst

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

FAQPage Schema
How do I calculate sample size and power for an A/B test?▼

To calculate sample size and power for an A/B test, you provide a hypothesis and baseline metric, which generates a complete experiment plan including primary metrics, guardrails, and statistical power analysis to ensure valid results.

What are guardrail metrics and why do I need them for experiment design?▼

Guardrail metrics are secondary measures specified in your experiment design to monitor for unintended negative impacts. You need them during A/B testing to ensure feature rollouts do not harm other product areas while tracking primary metric improvements.

How do I design a multivariate experiment and formulate hypotheses?▼

Designing a multivariate experiment involves using a structured framework to formulate hypotheses and specify experimental variables. This process generates a pre-registered analysis plan covering primary metrics, guardrails, and sequential testing considerations for valid interpretation.

Can I use this for feature rollout analysis and readouts?▼

Yes, you can use this for feature rollout analysis. It provides readout and decision guidance by checking practical significance, monitoring novelty effects, and evaluating segmentation considerations to drive data-informed product decisions.

What is the best way to interpret A/B test results and check practical significance?▼

The best way to interpret A/B test results is applying pre-registered analysis plans that check practical significance, monitor novelty effects, and evaluate segmentation. This ensures statistically rigorous readouts and clear decision guidance for product teams.

When should I pre-register my experiment analysis plan?▼

You should pre-register your experiment analysis plan before launching A/B tests or feature rollouts. Pre-registration specifies hypotheses, primary metrics, guardrails, and sample size calculations, preventing biased readouts and ensuring statistically valid decisions.