manage-feature-flags

Installation
SKILL.md

Manage Feature Flags

Engine required — resolve an engine per ENGINE.md: one named in the conversation or loaded instructions is mandatory (not set up → offer /mixpanel:install for it); otherwise use the Mixpanel MCP server, or offer /mixpanel:install if it's unavailable.

Coach the user through Mixpanel feature-flag work end-to-end: routing the request to the right flag-shaped product, ramping safely, killing fast when something goes wrong, and cleaning up when iteration is done.

The single most important idea: a flag's on/off state and its rollout percentage are different levers. The on/off state is the kill switch (instant). The rollout percentage is the throttle (gradient). Most flag bugs come from confusing the two; use the right lever for each step.

Requirements

  • Access to Mixpanel (read, create, update, list, and archive feature flags).
  • For experiment-backed flags, the ability to create and update experiments — see references/experiment-linked-flags.md.

When to use this skill

Trigger when the user asks anything about creating, configuring, ramping, killing, archiving, debugging, or cleaning up Mixpanel feature flags. Common phrasings:

Installs
15
GitHub Stars
18
First Seen
Jul 12, 2026