manage-experiment
Manage Experiment
Engine required — resolve an engine per
ENGINE.md: one named in the conversation or loaded instructions is mandatory (not set up → offer/mixpanel:installfor it); otherwise use the Mixpanel MCP server, or offer/mixpanel:installif it's unavailable.
This skill manages a Mixpanel experiment across its full lifecycle — design, launch, monitor, interpret. Four commands sit under the umbrella, picked by experiment phase (the state→command mapping lives in the Canonical commands section below).
The skill runs as a single interactive session per experiment. Commands compose naturally across phases — designing produces a configuration that launching commits, monitoring watches for safety issues mid-flight, interpreting consumes the matured result — but they're rarely invoked in the same session (the lifecycle spans days to weeks).
Components
The pieces the skill is built from. The Steps section below tells you how to use them.
Canonical commands
Each command lives in its own file under commands/ and is loaded on demand. Match commands explicitly (user names them) or implicitly (message matches a trigger phrase below).