Amplitude Taxonomy Guardian
Keep your Amplitude tracking plan consistent — audit, naming, schemas, and governance workflow
- What
- Keep your Amplitude tracking plan consistent — audit, naming, schemas, and governance workflow
- Cost
- Free
- Needs
- an Amplitude account with a tracking plan; the Amplitude MCP server configured; plan write access for governance actions
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a tracking-plan governance skill that keeps an Amplitude implementation consistent as it evolves. Covers the standard taxonomy workflow: verify or establish API connection to Amplitude, audit existing tracking (event counts, naming violations, schema mismatches), create or update tracking-plan branches and events, and manage schema validation so breaking changes surface before they ship. Pairs with `amplitude-mcp-marketplace` (published in this catalog as lot 24), which provides the MCP connection layer; this skill provides the governance methodology on top. Requires the Amplitude MCP server configured and a plan with write access — enterprise features. By @amplitude, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an Amplitude account with a tracking plan; the Amplitude MCP server configured; plan write access for governance actions Install "Amplitude Taxonomy Guardian" for me. Keep your Amplitude tracking plan consistent — audit, naming, schemas, and governance workflow Repository: https://github.com/amplitude/mcp-marketplace/blob/main/plugins/amplitude/skills/taxonomy/SKILL.md 1. Fetch the SKILL.md file for the amplitude-mcp-marketplace-taxonomy skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "amplitude-mcp-marketplace-taxonomy". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.