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. Show more Installs 905 Repository amplitude/mcp-m…ketplace GitHub Stars 32 First Seen Mar 31, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass

安装