Analytics instrumentation pipeline for a PR, branch or feature
End-to-end analytics instrumentation workflow — reads the code, discovers trackable events, and produces a concrete tracking plan
- What
- End-to-end analytics instrumentation workflow — reads the code, discovers trackable events, and produces a concrete tracking plan
- Cost
- Free
- Needs
- an analytics-tracked codebase (Amplitude or similar); the sibling skills diff-intake, discover-event-surfaces and instrument-events installed for the full pipeline; the Amplitude MCP server connected for live taxonomy reads (recommended)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Amplitude's official orchestrator skill for the analytics instrumentation pipeline. You point it at a PR, branch, file/directory, or a natural-language feature description; it captures the intent, builds a `change_brief` (via the `diff-intake` skill for PRs/branches, direct file reads for paths, git-history + codebase search for features), then chains the `discover-event-surfaces` and `instrument-events` skills to produce a tracking plan with exact file locations, tracking code and property definitions for every critical event. It stops honestly when no instrumentable events are found. By @amplitude, listed here with credit to its creator. Honest caveats: an orchestrator, not a solo skill — the full pipeline needs its sibling skills (`diff-intake`, `discover-event-surfaces`, `instrument-events`) installed too; connecting the Amplitude MCP server unlocks the live taxonomy/catalog reads; it produces a tracking plan for your review, it does not write the instrumentation code itself. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Analytics instrumentation pipeline for a PR, branch or feature is a free Muse skill that runs an end-to-end analytics instrumentation workflow: it reads the code, discovers trackable events, and produces a concrete tracking plan, so a new feature ships with the events needed to measure it, planned before the code merges.
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 analytics-tracked codebase (Amplitude or similar); the sibling skills diff-intake, discover-event-surfaces and instrument-events installed for the full pipeline; the Amplitude MCP server connected for live taxonomy reads (recommended) Install "Analytics instrumentation pipeline for a PR, branch or feature" for me. Give my agent Amplitude's official orchestrator for end-to-end analytics instrumentation — intent capture, change_brief building, event-surface discovery and tracking-plan generation Repository: https://raw.githubusercontent.com/amplitude/mcp-marketplace/e61691f81196cfd9f4314a347f6d2b1c6106f780/plugins/amplitude/skills/add-analytics-instrumentation/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 for the amplitude-mcp-marketplace-add-analytics-instrumentation skill from the repository into a temporary folder 2. Safety check: review the SKILL.md 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 into the agent's skills directory, in a folder named "amplitude-mcp-marketplace-add-analytics-instrumentation". 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. install the sibling skills and connect the Amplitude MCP server for the full pipeline). 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.