add-analytics-instrumentation
Analyticsamplitude/mcp-marketplaceskills.sh ↗
Installs
6,947
deduplicated, at the last sync
Since we started
+46.5%
40 readings, about 2 hours apart. Not a live curve.
Our category
Analytics
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill provides an end-to-end workflow for adding analytics instrumentation to code changes. It analyzes a Pull Request (PR), branch, file, or feature description to understand the scope of changes and automatically generates a concrete plan for tracking events.
- trackingPlan JSON with tracking code
- event_candidates YAML block
- change_brief YAML block
- PR URL or number
- Branch name
- File path or directory path
- Natural-language feature description
not detected
The evidence does not contain any information regarding paid service requirements.
not detected
The evidence does not contain any information regarding registration requirements.
It cannot decide or verify if the user wants to adjust the generated plan, nor can it proceed with implementation after generating the tracking plan. It also stops and reports an error if any step fails due to incomplete data.
Evidenceplugins/amplitude/skills/add-analytics-instrumentation/SKILL.md:1-146
--- name: add-analytics-instrumentation description: > 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. --- # add-analytics-instrumentation 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. ## Pipeline ### Step 0: Capture intent
Read 1 of 1 text files in the skill.
Installfrom the directory
npx skills add https://github.com/amplitude/mcp-marketplaceInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
1 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 4.7k, not zero — the range is 4.7k to 6.9k.