Instrument Events

Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate t

48 stars 12 forksData & Analytics 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 instrument-events
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/instrument-events ~/.claude/skills/instrument-events

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

From the SKILL.md

# instrument-events

You are step 3 of the analytics instrumentation workflow. You receive
`event_candidates` YAML (from discover-event-surfaces) and produce a concrete
instrumentation plan that an engineer can implement line-by-line.

Think like a **Software Architect** reviewing a PR: you care about consistency
with existing patterns, minimal footprint, and properties that actually power
dashboards — not vanity fields nobody queries.

Read the `taxonomy` skill at `../taxonomy/SKILL.md` to understand the core philosophy of analytics and event naming standards.

---

## 1. Filter to critical events

Parse the `event_candidates` YAML. Extract only candidates where `priority: 3`.
These are the events that would block a release — everything else is out of
scope for this skill.

If there are zero priority-3 events, tell the user and stop.

List the filtered events so the user can confirm scope before you proceed.

## 2. Load repo instrumentation context (`.amplitude/instrumentation-agent-context.md`)

Customers can commit `.amplitude/instrumentation-agent-context.md` (checked at
the repo root, or the subdirectory root if you're instrumenting a sub-tree). It
holds the customer's own instrumentation directives — taxonomy/naming
conventions, property standards, business context, SDK/wrapper patterns,
constraints, or simply a list of reference files already in the repo that
capture those conventions.

### 2a. If it exists
Read the full skill on GitHub

Details

Skill name
instrument-events
Path
plugins/amplitude/skills/instrument-events/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Instrument Events skill do?

Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate t

How do I install the Instrument Events 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 Instrument Events 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

Reskill

45

Azure-Samples/agent-skills-dotnet-demo

Team-wide charter and history optimization through skill extraction

Data & Analytics11

Discover Opportunities

48

amplitude/mcp-marketplace

Discovers product opportunities by analyzing Amplitude analytics, experiments, session replays, and customer feedback. Synthesizes evidence into prioritized, actionable opportunities with RICE scoring. Use when the user asks to "find opportunities", "what should we build", "where are we losing users", "product gaps", or wants a data-driven backlog of improvements.

Data & Analytics12

Scheduled Report Refresh

48

amplitude/mcp-marketplace

Refreshes recurring reports (daily briefings, WBRs, experiment briefs) from saved Amplitude content — fetch the dashboard, re-pull its charts, fill gaps with ad hoc queries, summarize deltas. Use for "run the daily/weekly report", "refresh this dashboard's numbers", or scheduled custom-agent report runs.

Data & Analytics12

Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.