instrument-events: a Claude Code skill by Amplitude
Official
For product teams adding Amplitude tracking who want each call placed at the right line of code. Skip it if you haven't run discover-event-surfaces or don't use Amplitude.
- Score
- 78of 100
- Rank
- #79of 239
- Installs
- 57.3Kon skills.sh
- Security
- Clear 3 scanners
- Updated
- 2026
- Context
- ~210tokens always
Install
npx skills add https://github.com/amplitude/mcp-marketplace --skill instrument-events Run it in your terminal. View the source
Using the Claude app rather than Claude Code? You can add a skill there too. How to add it in the app
What does instrument-events do?
instrument-events is a skill that turns Amplitude event candidates into an exact tracking plan, as step three of Amplitude's instrumentation workflow. It takes the event_candidates YAML from discover-event-surfaces, keeps only priority-3 events, and asks you to confirm the list. It reads .amplitude/instrumentation-agent-context.md for your naming rules and needs .amplitude/instrumentation-agent.yaml to map file paths to app IDs. For each event it reads the hinted file, finds where the outcome is confirmed, and picks 2 to 4 in-scope properties. The output is a JSON trackingPlan with file paths, line numbers and code. After you agree, high-confidence events go into Amplitude through MCP.
When should you use instrument-events?
Use it when
- You have event_candidates YAML and want tracking code
- You want to know where each track() call belongs
- You want critical events added to your Amplitude tracking plan
Skip it when
- You haven't run discover-event-surfaces yet
- Your product doesn't use Amplitude
What it needs and what it can touch
You need
- An Amplitude account with the Amplitude MCP server connected
- event_candidates YAML from the discover-event-surfaces skill
- The companion taxonomy and discover-analytics-patterns skills
What it can do
- Reads project files
- Writes .amplitude/instrumentation-agent.yaml after you confirm
- Creates events and properties in Amplitude through MCP after you confirm
From reading its instructions, not from running it.
Why it scores 78
Strongest on upkeep (100 of 100), weakest on adoption (43).
Is instrument-events safe to install?
Every scanner that checked it passed it. Scanners often miss what other scanners catch, and a skill can change after a scan. Read its source before you install it.
| Scanner | Result | Date |
|---|---|---|
| Gen Agent Trust Hub | Passed | Sep 15, 2026 |
| Socket | Passed | Sep 15, 2026 |
| Snyk | Low risk | Sep 15, 2026 |
Details
- Installs
- 57,333
- Repository stars
- 47
- Last repository change
- Tokens always loaded
- about 210
- Tokens when used
- about 3,634
- License
- MIT
- Data confidence
- High
Did it do the job for you?
Alternatives to instrument-events
All skills for this job- Get add-analytics-instrumentation
add-analytics-instrumentation
For product teams on Amplitude who want a tracking plan drawn from a PR, branch, file or feature.
- Get diff-intake
diff-intake
For teams adding analytics tracking who want a PR turned into a YAML change brief.
-
Get clickhouse-best-practicesclickhouse-best-practices
For teams designing or reviewing ClickHouse tables, queries and inserts against the vendor's own rules.
instrument-events