Monitor Experiments Consolidated

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

48 stars 12 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add amplitude/mcp-marketplace

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add amplitude/mcp-marketplace --skill monitor-experiments-consolidated
Manual install
git clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude/skills/monitor-experiments-consolidated ~/.claude/skills/monitor-experiments-consolidated

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Experiment Monitor & Report Generator

Scan active and recently completed experiments, surface what needs attention, and report on the ones that matter.

This is a **monitoring** skill — keep output accessible to non-experts. Avoid statistical jargon (no p-values, no power analysis). For deep-dive analysis of a specific experiment, use the `analyze-experiments` skill instead.

---

## CRITICAL: Managing Response Sizes

1. **`use_amp_experiments` action `get`: 3-5 IDs max per call.** Filter using `search_amp_entities` results BEFORE fetching.
2. **`use_amp_experiments` action `analyze` responses are large.** Extract only `summary` objects and validity flags. Ignore `timeseries`, `xValues`, bulk arrays.
3. **Metric name resolution**: `search_amp_entities` does NOT match metric IDs in `queries`. Search with `entityTypes: ["METRIC"]`, empty `queries`, `limitPerQuery: 50`, scoped to project. Match IDs from results.

---

## Report Structure

The report has two parts:

1. **Summary & Actions** (top) — One table + action items. Someone should be able to read just this and know the full picture.
2. **Details** (bottom) — Deep-dives on experiments that need attention, briefs on recently decided, one-liners for monitoring experiments, and a needs-setup list.

Do NOT duplicate information between the summary table and the details. The summary table is the single source of truth for the portfolio state. Details expand on specific experiments.

---

## Instructions
Read the full skill on GitHub

Details

Skill name
monitor-experiments-consolidated
Path
plugins/amplitude/skills/monitor-experiments-consolidated/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Monitor Experiments Consolidated skill do?

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

How do I install the Monitor Experiments Consolidated skill?

Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Monitor Experiments Consolidated popular?

It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.

Related skills

Add Analytics Instrumentation

48

amplitude/mcp-marketplace

End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature

Data & Analytics12

Analyze Account Health

48

amplitude/mcp-marketplace

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

Marketing, Sales & Business12

Analyze AI Topics

48

amplitude/mcp-marketplace

Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.

AI, LLMs & Agents12

Monitor Reliability

48

amplitude/mcp-marketplace

Delivers a reliability health check using auto-captured network request, JS error, and error click data. Use when the user asks for a "reliability check", "error rate", "quality metrics", "page health", "did the release break anything", "error budget", or wants a proactive product quality report.

Other12

Monitor Experiments

48

amplitude/mcp-marketplace

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

Other12

Release Process

45

Azure-Samples/agent-skills-dotnet-demo

Step-by-step release checklist for Squad — prevents v0.8.22-style disasters

Other11

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.