add-analytics-instrumentation skill (Amplitude): plan analytics events for a PR, file or feature

Amplitude's own skill that has a coding agent turn a PR, branch, file or feature into a tracking plan for Amplitude events.

Installs: 48.8K; on skills.sh
Stars: 46; on GitHub
Updated: Oct 2026; last repo commit

add-analytics-instrumentation makes your coding agent turn a pull request, branch, file or feature description into a concrete analytics tracking plan. It reads the code, works out which events matter, and lists where each tracking call goes and which properties it sends.

It is an orchestrator. It calls diff-intake, discover-event-surfaces and instrument-events in order, so those must be installed too. It produces a plan and asks before any implementation. The last step can add events to your Amplitude project through the Amplitude MCP, after you confirm.

Good for

Product engineers who need analytics added to a PR or feature
Reviewers who want an analytics coverage check on a branch
PMs who want to see candidate events before engineering starts

Install add-analytics-instrumentation

Claude Code

Copy this prompt.

Install the add-analytics-instrumentation skill in Claude Code. Run this command:

claude plugin install amplitude

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

The plugin installs all 36 Amplitude skills and registers the Amplitude MCP server; run /mcp, pick the amplitude server and sign in in the browser. The skills CLI route installs only the 6 skills this workflow needs: add-analytics-instrumentation calls diff-intake, discover-event-surfaces and instrument-events; instrument-events calls discover-analytics-patterns; and the skills read taxonomy. With that route add the Amplitude MCP server yourself. You need an Amplitude account.

From the project README. Source.

What's in the skill

When it loads

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 description and mentions analytics, events, or instrumentation. This is the main entry point for the analytics workflow — prefer it over calling the individual steps (diff-intake, discover-event-surfaces, instrument-events) separately.

Sections in SKILL.md

Pipeline
Step 0: Capture intent
Step 1: diff-intake skill (PR or Branch)
Step 1a: Direct file read (File / Directory)
Step 1b: Feature search (Feature)
Step 2: discover-event-surfaces
Step 3: instrument-events
Presenting the result
Error handling

Key facts

Author: Amplitude (vendor's own repo; the README calls it the official Amplitude plugin)
License: MIT (LICENSE file, README and plugin manifests agree)
Installs on skills.sh: 48,809 as of 2026-11-02
GitHub stars: 46 for the whole mcp-marketplace repo, 2026-11-02
What is inside: 1 file: SKILL.md. It bundles no scripts, and it calls three sibling skills.
Last change to this skill: 2026-07-06
Part of: The amplitude plugin (version 1.7.0 in the marketplace file) in the amplitude marketplace
Works in: Claude Code, Cursor, Codex, Gemini CLI and Claude, per the README

What it includes

Works out whether you gave a PR, branch, file or feature
It infers from a URL or number, a branch name, an existing path, or a description, and asks only if it is truly unclear.
Try: “Instrument PR #42.”
Read · Step 0: capture intent
For a PR or branch, builds a change brief
Invokes the diff-intake skill, which uses gh and git, and keeps the YAML change brief it returns.
Runs code · Step 1: diff-intake
For a file or directory, builds the brief itself
Reads the files, looks for existing track and logEvent calls, and sets analytics_scope to high.
Read · Step 1a: direct file read
For a description, finds the code first
Searches git history with git log --grep, then greps and globs the codebase for related files.
Runs code · Step 1b: feature search
Lists candidate events for the change
Produces an event_candidates YAML. If there are none it stops and says so.
Network · Step 2: discover-event-surfaces
Produces the tracking plan JSON
Outputs exact file locations, tracking code and properties for each critical event. That skill can also add the events to your Amplitude project after you confirm.
Write · Step 3: instrument-events
Walks through each event and asks what to adjust
For each event it says what it tracks, which Amplitude project it routes to, where the call goes and which properties it sends.
Read · Present the result
Stops on a failed step
If the PR does not exist or git fails, it reports the error and does not continue with incomplete data.
Read · Error handling

From the official docs

Permissions

Medium risk

The agent runs git and gh commands, reads your source, and its last step can create events and properties in your Amplitude project. Check the list of events before you confirm, and review the plan before any code is changed.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It can create events and properties in your Amplitude project
The instrument-events step, which this workflow ends in, uses the Amplitude MCP to create events and properties in your tracking plan after you confirm, and only for events routed with high confidence. Read the list it shows before you say yes. github.com
It may write .amplitude/instrumentation-agent.yaml
If that mapping file is missing, instrument-events can offer to scan your repo and write it with the Write tool, but only after you confirm the app IDs. SKILL.md says it never invents numeric app IDs. github.com
Plans are shown before code changes
The skill ends by presenting the tracking plan and asking whether to adjust or proceed to implementation. Check what you approve at that point. github.com
The plugin route installs 36 skills and the Amplitude MCP config
The git tree holds 36 skill folders under plugins/amplitude/skills, while the README lists 27. The plugin also bundles .mcp.json for https://mcp.amplitude.com/mcp, which you sign in to. The README lists skills that create charts and dashboards. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Talks to	GitHub, through the gh CLI. mcp.amplitude.com (Amplitude MCP server)
Sign-in and keys	You sign in to the Amplitude MCP server in the browser from /mcp. PR access uses your gh login.
Scopes	Runs gh pr view, git log and git diff through diff-intake, and git log --grep, grep and glob for feature search Reads source files in your repo Through instrument-events: may write .amplitude/instrumentation-agent.yaml after confirmation Through instrument-events: uses manage_amp_events and create_properties on the Amplitude MCP to create events and properties after explicit confirmation

Questions

What does add-analytics-instrumentation do?

It has your coding agent read a PR, branch, file or feature and produce a tracking plan: which analytics events to add, where the calls go in the code, and which properties each sends.

How do I install add-analytics-instrumentation?

Use the install box at the top of this page. It must be installed with diff-intake, discover-event-surfaces and instrument-events, which it invokes, with discover-analytics-patterns, which instrument-events invokes, and with taxonomy, which the skills read. The skills CLI route installs those six and the plugin route installs all 36 Amplitude skills.

Does it need an Amplitude account?

Yes. The README lists an Amplitude account with API access as a requirement, and you sign in to the Amplitude MCP server from /mcp. Some steps read your existing events from Amplitude.

Does it change my code or my Amplitude data?

It ends by presenting a plan and asking how to proceed. The instrument-events step can add events and properties to your Amplitude project through the MCP, but SKILL.md says it lists them and gets explicit confirmation first.

Is add-analytics-instrumentation safe?

It runs git and gh commands and can write to your Amplitude tracking plan after you confirm. Check the event list and the project it names before you say yes.

add-analytics-instrumentation or the individual steps?

SKILL.md calls it the main entry point and says to prefer it over calling diff-intake, discover-event-surfaces and instrument-events separately.

Is this the official Amplitude skill?

Yes. It is in Amplitude's own mcp-marketplace repo, which the README calls the official Amplitude plugin.

Does it work in the Claude app, Codex or Cursor?

The README names Claude Code, Cursor, Codex, Gemini CLI and Claude, and gives install steps for the first four. The skill runs git and reads your repo, so there is no Claude app upload option here.

Information

updated Nov 2, 2026

Repository: amplitude/mcp-marketplace
Folder: plugins/amplitude/skills/add-analytics-instrumentation

amplitude/mcp-marketplace skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7

README.md · github.com
marketplace.json · github.com
.mcp.json · github.com
plugin.json · github.com
SKILL.md · github.com
SKILL.md · github.com
SKILL.md · github.com