Amplitude analytics instrumentation planner
Turn event candidates into a line-by-line Amplitude tracking plan with per-event app-id routing
- What
- Turn event candidates into a line-by-line Amplitude tracking plan with per-event app-id routing
- Cost
- Free
- Needs
- an Amplitude account (a free plan exists) and the Amplitude MCP server connected to the agent; for multi-project routing, an .amplitude/instrumentation-agent.yaml in the repo
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @amplitude's own skill for step 3 of their analytics instrumentation workflow: it takes `event_candidates` YAML (produced by their discover-event-surfaces skill), filters to priority-3 critical events, reads repo conventions (`.amplitude/instrumentation-agent-context.md`) and the path→app-id mapping (`.amplitude/instrumentation-agent.yaml`), inspects the hinted files to find the exact insertion point and in-scope variables for each tracking call, designs minimal chart-useful properties (2–4 per event), and outputs a structured JSON tracking plan — with explicit confirmation before anything is written back to Amplitude via MCP. Honest caveats: requires an Amplitude account (a free plan exists) plus the Amplitude MCP integration; works best on the output of the sibling discover-event-surfaces skill; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Amplitude analytics instrumentation planner is a free Muse skill that turns event candidates into a line-by-line Amplitude tracking plan with per-event app-id routing, so each event is specified, routed to the right app, and ready to implement, instead of remaining a vague list of things worth tracking someday.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e61691fStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an Amplitude account (a free plan exists) and the Amplitude MCP server connected to the agent; for multi-project routing, an .amplitude/instrumentation-agent.yaml in the repo Install "Amplitude analytics instrumentation planner" for me. It takes event_candidates YAML and generates a concrete, line-by-line instrumentation plan (insertion points, properties, app-id routing) that an engineer implements — nothing is written to Amplitude without explicit user confirmation. Repository: https://raw.githubusercontent.com/amplitude/mcp-marketplace/e61691f81196cfd9f4314a347f6d2b1c6106f780/plugins/amplitude/skills/instrument-events/SKILL.md Pinned version: install the code at commit e61691f81196cfd9f4314a347f6d2b1c6106f780 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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 "instrument-events". 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. connect the Amplitude MCP server, add my Amplitude app ID to the .amplitude config, get event candidates from the discover-event-surfaces skill first). 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. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- e61691f · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.