Taxonomy

Taxonomy is a reference skill for Amplitude event tracking plans. It's the thing an agent reads before it proposes event names, property names, or cleanup work, so the advice stays consistent with Amplitude's own rules. The source covers naming conventions, property standards, a scoring framework for audits, and a deprecation procedure that separates "stale" from "unused" before anything gets blocked or deleted. It also draws a sharp line between reducing event volume (blocking or deleting) and reducing type counts (only deleting works, since blocking and hiding leave the type count alone). My take: the most useful part is the explicit rule that agents must confirm before any write and never recommend sampling, since those are the mistakes an eager assistant would otherwise make on a live Amplitude project.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Taxonomy Generation & Data Auditing

When to Use

User asks to create or review a tracking plan or event taxonomy
User wants to validate event/property naming conventions
User asks to audit or review a plan or branch against "our standard", their naming settings, or their AI Context
User needs to audit data quality (duplicates, stale events, missing metadata)
User asks about funnel design or event relationships
Agent is generating event names or property names and needs to follow standards
User wants to understand or improve their taxonomy governance
User asks about reducing event volume or type counts
User asks about deprecation, blocking, deleting, or hiding events
Any agent needs a "source of truth" for taxonomy best practices before recommending events
User asks about AI readiness, AI Controls, or improving AI feature accuracy