Terminal
Terminal/Skill
Turns a loose experiment name, status, or word like latest into the exact experiment ID, asking you to choose if several match.
By PostHog
Works with
npx skills add posthog/ai-plugin --skill finding-experimentsUsers refer to experiments by name, description, or relative references — not by ID. This skill resolves natural language references to concrete experiment IDs.
Use the experiment-list tool from the Posthog-local MCP server.
IMPORTANT: Do NOT use feature-flag-get-all or any feature flag tool to find
experiments. Use the dedicated experiment list tool: experiment-list.
This tool returns experiments with their id, name, status, feature_flag_key, start_date, end_date, and created_at. Browse the returned list to find the experiment matching the user's reference:
name field for matchesstatus field (draft, running, paused, exposure_frozen, stopped)experiment-get-by-flag-key with the key. It returns the
full experiment, or found: false with a reason. no_flag and no_experiment mean the key is
free, so this is also the existence check to run before experiment-create. ambiguous means
several experiments share the flag and none is the single live one: show the candidates and
pick one with experiment-get rather than creating another.After resolving to an ID, call experiment-get for the full object (metrics, flag details, parameters).
User: "pause my signup experiment"
Agent:
1. Calls experiment-list
2. Scans results, finds "New signup process" (ID: 1371, status: running)
3. Proceeds to pause experiment 1371
managing-experiment-lifecycle — act on the experiment once you've resolved its IDdiagnosing-experiment-results — investigate the experiment you found