Instrument Events

Instrument-events takes the priority-3 (critical) entries from a discover-event-surfaces YAML and turns them into a concrete trackingPlan JSON that says exactly where each tracking call belongs. It acts like a reviewing architect: it reads the hinted files, checks which variables are actually in scope at the insertion point, keeps properties to the handful a dashboard would query, and follows the repo's existing analytics patterns rather than inventing new ones. It also routes each event to the right Amplitude project using a required .amplitude/instrumentation-agent.yaml mapping, and it will stop and ask rather than guess app IDs. Reach for it as step 3 once you have event candidates and want implementation guidance instead of a wish list. The main thing to set up first is that routing file, since high-confidence write-back depends on it.

skills.sh installs: 55.4K
GitHub stars: 47
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add amplitude/mcp-marketplace --skill instrument-events --agent claude-code

Installs into .claude/skills of the current project.

Files

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.