What it does. You are the orchestrator for the analytics instrumentation pipeline. Your job is to figure out what the user wants to instrument, gather the relevant code, and run the pipeline to produce a tracking plan.
Before running anything, determine what the user wants to instrument. There are four input types — infer the type from what the user has already provided in the conversation. Only ask if it's genuinely ambiguous.
Highlights
- If the user provided a URL or
#number
→ PR
- If the user provided something that looks like a branch name (contains
/
, no file extension, matches a git branch) → Branch
- If the user provided a path that exists on disk (file or directory) → File / Directory
- If none of the above match and the input is descriptive → Feature
- If the conversation already contains a PR link, branch name, or file path from earlier messages, use that instead of asking again
When to use it. 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…
Install
npx skills add amplitude/mcp-marketplace --skill add-analytics-instrumentation
Or copy the skill folder manually:
git clone https://github.com/amplitude/mcp-marketplace.git
cp -r mcp-marketplace/plugins/amplitude/skills/add-analytics-instrumentation/ ~/.claude/skills/add-analytics-instrumentation
Source: amplitude/mcp-marketplace — 34 stars, MIT, last pushed 2026-08-24.
