Experiment Tracker

Designs, tracks, and analyzes A/B tests and feature experiments with statistical rigor.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill experiment-tracker-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Experiment Tracker
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/project-management/experiment-tracker
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill experiment-tracker-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often launch product changes based on intuition rather than evidence, leading to unreliable decisions and wasted engineering effort. This Skill provides a systematic framework for designing statistically valid experiments, tracking their execution, and turning results into clear go/no-go decisions. ## Core Features & Use Cases - Experiment Design: Creates hypotheses with measurable success criteria, calculates required sample sizes for 80% power, and structures control/variant groups with proper randomization. - Execution Tracking: Manages experiment portfolios across product areas, monitors data collection quality, and enforces safety monitoring with rollback procedures. - Statistical Analysis & Reporting: Performs significance testing, confidence interval calculation, and segment analysis, then delivers structured results documents with business impact estimates. - Use Case: A product team wants to test a new checkout flow. Use this Skill to design the A/B test with proper sample sizing, monitor it during runtime, and receive a final report stating the conversion lift with 95% confidence and a rollout recommendation. ## Quick Start Ask the Experiment Tracker to design an A/B test for your new checkout flow with a hypothesis, success metrics, and required sample size.

Frequently Asked Questions about Experiment Tracker

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

FAQPage Schema
How do I design an A/B test with proper statistical significance?▼

A/B test design requires a clear hypothesis, measurable primary metrics, and a sample size calculation targeting 80% statistical power. The Skill generates an experiment design document covering variants, population criteria, duration, and risk assessment before launch.

How to calculate sample size for an A/B test?▼

Sample size calculation depends on baseline conversion rate, minimum detectable effect, significance level (typically 95%), and desired power (typically 80%). The Skill computes required users per variant so experiments reach statistical significance without stopping early.

What metrics should I track in a feature experiment?▼

Track one primary KPI tied to your hypothesis, secondary metrics for additional insight, and guardrail metrics that detect user experience degradation. The Skill's design template structures all three categories with explicit success and failure thresholds.

Can I stop an A/B test early when results look significant?▼

Stopping experiments early without proper early stopping rules inflates false positive rates. The Skill enforces pre-defined runtime and significance criteria, and supports sequential testing methods when early decisions are genuinely needed.

What are the limitations of A/B testing for product decisions?▼

A/B testing cannot measure long-term effects, novel feature reactions, or interactions between concurrent experiments without special designs. For these cases, the Skill supports multi-armed bandits, holdout groups, and cross-experiment interference detection.