Tracking Plan Audit

Use when auditing Amplitude tracking plans for safe deletion candidates among stale, duplicate, orphaned, cross-app, retired, high-volume, generated-client, never-ingested, or deleted-but-still-emitted events and event properties.

48 stars 12 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add amplitude/mcp-marketplace

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add amplitude/mcp-marketplace --skill tracking-plan-audit
Manual install
git 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/tracking-plan-audit ~/.claude/skills/tracking-plan-audit

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Tracking Plan Audit

Produce a deletion-focused, evidence-backed cleanup inventory. This skill
specializes in deletion audits across telemetry, source code, ownership,
dependencies, and tracking-plan branches. Use `taxonomy` for broad taxonomy
design, naming, metadata, and governance guidance.

Do not add or restore taxonomy objects, make metadata-only changes, or create,
mutate, merge, or delete an Amplitude branch unless the user explicitly asks.

At the start, establish:

- the Amplitude project and environment;
- whether the goal is lower ingestion volume, fewer taxonomy types, or both;
- every repository or directory that may emit the project's data;
- the requested audit mode and lookback window.

## Source-code gate

Source code is required. If the user has not identified every repository or
directory that can emit into the project, ask for those locations before
recommending deletion candidates. You may inventory taxonomy objects while
waiting, but label the result incomplete and do not recommend or execute any
deletion. Before lifting this gate, ask the user to confirm that the supplied
source inventory covers every known emitter.
Never report "no code reference" unless every user-identified source root was
searched.

Do not assume repository names, services, languages, project IDs, event names,
observability systems, or filesystem layouts. Inspect each source root's local
instructions before searching it.

## Route the audit
Read the full skill on GitHub

Details

Skill name
tracking-plan-audit
Path
plugins/amplitude/skills/tracking-plan-audit/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Tracking Plan Audit skill do?

Use when auditing Amplitude tracking plans for safe deletion candidates among stale, duplicate, orphaned, cross-app, retired, high-volume, generated-client, never-ingested, or deleted-but-still-emitted events and event properties.

How do I install the Tracking Plan Audit 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 Tracking Plan Audit popular?

It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.

Related skills

Add Analytics Instrumentation

48

amplitude/mcp-marketplace

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

Data & Analytics12

Analyze Account Health

48

amplitude/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.

Marketing, Sales & Business12

Analyze AI Topics

48

amplitude/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.

AI, LLMs & Agents12

Weekly Brief

48

amplitude/mcp-marketplace

Delivers a weekly briefing summarizing the most important trends, wins, and risks across your Amplitude instance. Use when the user asks for a "weekly review", "weekly summary", "week in review", "what happened this week", or wants a recap of the past 7 days to share with their team or leadership.

Other12

Reviewing Changes

33

okgrit/done-is-a-claim

Review an actual candidate against the user's acceptance and scope, then carry findings through fixes, affected checks and rereview. Use before claiming a substantive change complete or accepting a worker's implementation.

OtherIn 1 list

Haizei Cyberpunk Terminal Ppt

43

wuchubuzai2018/expert-skills-hub

生成赛博朋克终端控制台风格的网页 PPT(HTML 单文件)。设计语言是把 PPT 伪装成正在被解构/调试的开发者控制台。典型场景用户说做个赛博朋克风的网页 PPT、帮我做一份终端风格的演示稿、用 cyberpunk terminal 风格讲 xxx。

Other

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.