Add Analytics Instrumentation

Point this at a PR, branch, file, directory, or even a plain-English feature description like "the checkout flow," and it runs the whole analytics pass in one go: reads the code, finds the events worth tracking, and emits a tracking plan with file locations, call sites, and property definitions. It chains three sub-skills (diff-intake, discover-event-surfaces, instrument-events) so you don't have to, and it's smart about routing: direct file reads skip the diff step, and feature searches fall back to grepping git history and the codebase. The honest take is that the quality ceiling depends on how well the feature search resolves to real files, so vague descriptions are where it'll need the most nudging. For a clear PR, it's the fastest path from "I changed code" to "here's what to track."

skills.sh installs: 55.6K
GitHub stars: 47
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add amplitude/mcp-marketplace --skill add-analytics-instrumentation --agent claude-code

Installs into .claude/skills of the current project.

Files

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

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.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly