add-analytics-instrumentation
End-to-end analytics instrumentation workflow for a PR, branch, file, directory
by amplitudeFree
Description
add-analytics-instrumentation is an agent skill that runs an end-to-end workflow for adding analytics events to code. It is the orchestrator for a pipeline that takes a pull request, a branch, a file, a directory or a feature, reads the code, works out which events should be tracked, and produces a tracking plan. Its first step, capturing intent, works out which of the four input types the user has given, and it asks a question only when the request is unclear. From there the skill runs the pipeline's steps in order, which are described by the other Amplitude skills: a diff intake that turns the change into a structured brief, a discovery step that lists candidate events, an instrumentation step that plans the code changes for the most important events, and a step that studies how analytics calls are written in the codebase so new events match. The skill is part of the amplitude mcp-marketplace repository and is added to a compatible agent with the skills command. It is useful for product and engineering teams who want consistent analytics added as features ship. The Amplitude team's taxonomy skill provides the naming standards the pipeline follows.…
Highlights
- Runs the full instrumentation pipeline
- Accepts a PR, branch, file, directory or feature
- Produces a tracking plan
- Follows the Amplitude taxonomy standards
Ratings & Reviews
No ratings yet
Be the first to rate add-analytics-instrumentation.
People also visit
discover-analytics-patterns
Discovers how analytics tracking calls are actually written in this codebase
add-analytics-instrumentation FAQ
What does this skill do?
It orchestrates a workflow that reads code, decides which analytics events to track, and produces a tracking plan.
What inputs can it take?
A pull request, a branch, a file, a directory or a feature, which it infers from the conversation.
What does it produce?
A tracking plan that an engineer can implement, built from the events the pipeline finds.
Which naming standards does it use?
The taxonomy skill from the same Amplitude repository, which the pipeline reads for event naming and analytics philosophy.
How do I install it?
Run: npx skills add https://github.com/amplitude/mcp-marketplace --skill add-analytics-instrumentation
What security audits has it passed?
Gen Agent Trust Hub and Socket passed. Snyk shows a warning.
What are the best add-analytics-instrumentation alternatives?
Popular alternatives to add-analytics-instrumentation include instrument-events, diff-intake and discover-analytics-patterns. See all add-analytics-instrumentation alternatives