mcpbeat

Finding Experiments

posthog/posthog-foss-finding-experiments

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.

This is a copy. The original lives at posthog/ai-plugin-finding-experiments.

637 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
690
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/PostHog/posthog-foss --skill finding-experiments

The instruction itself

6 sections, as written by the author

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, feature_flag_key,

start_date, end_date, 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 feature_flag_key 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

How to use it

Copy the folder

Take posthog/posthog-foss-finding-experiments from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.