Add Analytics Instrumentation
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
Install
/plugin marketplace add amplitude/mcp-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add amplitude/mcp-marketplace --skill add-analytics-instrumentationgit clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude/skills/add-analytics-instrumentation ~/.claude/skills/add-analytics-instrumentationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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. | Input type | How to recognize it | Example | | -------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | | **PR** | A PR URL, PR number, or phrases like "this PR", "my PR" | `instrument PR #42`, `https://github.com/org/repo/pull/42` | | **Branch** | A branch name or "this branch", "my branch", "current branch" | `instrument feature/checkout`, `add tracking to this branch` | | **File / Directory** | A file path, directory path, or glob pattern | `instrument src/components/Checkout.tsx`, `add analytics to src/payments/` |
Details
- Skill name
add-analytics-instrumentation- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude/skills/add-analytics-instrumentation/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Add Analytics Instrumentation skill do?
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
How do I install the Add Analytics Instrumentation skill?
Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Add Analytics Instrumentation popular?
It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.
Related skills
Analyze Account Health
48amplitude/mcp-marketplace
Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.
Analyze AI Topics
48amplitude/mcp-marketplace
Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.
Analyze Chart
48amplitude/mcp-marketplace
Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.
Scrapy Extra
33zytedata/claude-skills
Read this BEFORE writing, modifying, debugging, or explaining any Scrapy or web-poet code — spiders, page objects, pipelines, settings, selectors — down to a one-line fix, or scaffolding/configuring a Scrapy project, scrapy-poet, scrapy-zyte-api, or browser rendering. These libraries moved on since your training cutoff; invoke this FIRST. NOT for building a scraper for a given site (scrape), a saved HTML file (scrape-analyze-page), or Scrapy Cloud deploy/jobs (zyte).
Analyze Dashboard
48amplitude/mcp-marketplace
Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends
Scrape Plan
33zytedata/claude-skills
Plan a web scrape and author a validated extraction spec — explore a detail page, discover fields, confirm the schema, then validate it with more pages, HTML-variant comparison, extracted values, and an optional browser review, and present the plan for approval.
Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.