AutoGineer
Generated banner for Finding Experiments
Generated logo for Finding Experiments

Finding Experiments

PostHogOfficialPublished by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured workflow for agents to translate human-readable experiment references into concrete IDs within PostHog. It ensures agents correctly identify the intended experiment by searching, filtering, and disambiguating results from the experiment list, preventing errors caused by using incorrect tools or ambiguous identifiers.

What it does

  • Searches for experiments using natural language names, descriptions, or relative time references.
  • Filters experiment results by status, name, or feature flag key.
  • Handles disambiguation when multiple experiments match a user's query.
  • Provides a fallback mechanism for when no matching experiment is found.
  • Integrates with specific PostHog tools to retrieve full experiment details once an ID is resolved.

When to use it

  • When a user refers to an experiment by name or description rather than an ID.
  • When a user uses relative time references like 'latest' or 'created yesterday'.
  • When an agent needs to confirm the existence or status of an experiment before performing an action.
  • When multiple experiments share similar names and require user clarification.

Advantages

  • Reduces user friction by allowing natural language interaction.
  • Prevents errors by enforcing the use of dedicated experiment tools over feature flag tools.
  • Provides clear protocols for handling ambiguous or missing experiment data.
  • Standardizes the process of experiment identification across different agent tasks.

Usage examples

“Pause my signup experiment.”
The agent calls the experiment list, identifies the 'New signup process' experiment, and proceeds to pause it.
“Show me the status of the latest pricing test.”
The agent searches for recent experiments, identifies the most recent one matching 'pricing', and retrieves its current status.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/finding-experiments/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip finding-experiments.zip -d .agents/skills

Documentation by PostHog

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

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/omnibus/finding-experiments · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download finding-experiments.zip