Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a r…
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match.
Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a relative reference ("latest", "most recent", "the one I created yesterday"), filters by status (running, draft, paused, exposure frozen, stopped, archived), or otherwise refers to an experiment by anything other than its concrete ID.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars80
LicenseMIT
Default branchmain
Open issues10
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,739 B
docsSUMMARY.md1,041 B
History
First seen on skills.sh
First recorded snapshot · 241 installs
SKILL.md
Finding experiments
Users refer to experiments by name, description, or relative references — not by ID. This skill resolves natural language references to concrete experiment IDs.
How to find an experiment
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, featureflagkey, startdate, enddate, and created_at. Browse the returned list to find the experiment matching the user's reference:
By name: scan the name field for matches
By recency: results are ordered newest first by default
By status: match the status field (draft, running, paused, exposure_frozen, stopped)
By flag key: match the featureflagkey field
After finding matches
Exactly one match: Use it. Confirm with the user by name before destructive actions (delete, ship, end).
Multiple matches: List them with name, status, and creation date. Ask the user to pick.
No matches: Tell the user. Suggest checking archived experiments or different terms.
Get full details if needed
After resolving to an ID, call experiment-get for the full object (metrics, flag details, parameters).
Examples
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
When NOT to search
You already have the experiment ID from earlier in the conversation
The user just created the experiment — you have the ID from the create response
The user provided the ID directly
Related skills
managing-experiment-lifecycle — act on the experiment once you've resolved its ID
diagnosing-experiment-results — investigate the experiment you found
