mcpField
F
finding-experiments

finding-experiments

github.com/posthogData & databases95350 installsUpdated today
Repository

About finding-experiments

A skill for resolving natural-language references to PostHog experiments into concrete experiment IDs. It uses experiment-list and explains how to handle ambiguous or missing matches.

Key features

  1. 01Finds experiments by name or recency
  2. 02Searches by status or partial flag key
  3. 03Resolves a flag key to its experiment
  4. 04Guides handling of multiple or missing matches

Use cases

  1. 01Finding an experiment before changing its settings
  2. 02Distinguishing experiments with similar names
  3. 03Checking whether a flag key has an experiment

MCP support

Directs agents to use the Posthog-local MCP server's experiment-list tool, and experiment-get-by-flag-key or experiment-get when needed.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/ai-plugin --skill finding-experiments

After installing, type/finding-experimentsin Claude Code to confirm it loaded.

Details

From the project README

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: skip the list and call 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.
  • By partial flag key: call experiment-list with search set to the fragment. search matches substrings of the experiment name and the flag key, ignoring case.

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-health — investigate the experiment you found

Comments

Markdown supported