Instrument Events
Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events.
- installs
- 41.2K
- GitHub stars
- 46
- last updated
- Oct 26, 2026
Install
$ npx -y skills add amplitude/mcp-marketplace --skill instrument-events --agent claude-codeInstalls into .claude/skills of the current project.
Sponsors
CodeRabbitSponsoredTry For Free
Lid closed, agents workingTry it
Open StepsSponsoredDownload for free
AppSignalSponsoredStart Free Trial
Keep API keys from agentsGet Snug
Block apps on your iPhoneGet Wax
Devtools for design engineersTry it live
belt - the only tool your agent needsSponsoredone prompt installWhat it does
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 tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.
Files
Select a file.
Details
- Repository
- github.com/amplitude/mcp-marketplace
- Categories
- Code Review & Quality, AI & Agent Building, Data Science & ML, Productivity & Planning, Automation & Workflows, Marketing & SEO
- First seen
- Oct 26, 2026
