discover-analytics-patterns
Discovers how analytics tracking calls are actually written in this codebase
by amplitudeFree
Description
discover-analytics-patterns is an agent skill that finds out how a codebase actually sends analytics events. Rather than listing which events exist, it finds the concrete code patterns that engineers use to fire a tracking call, such as the SDK calls, the function signatures and the import patterns. The output helps new events match the rest of the code, and it tells the downstream skills how event names and property names are usually written in that project. The skill uses a strict order of sources for naming conventions. Customer directives in an instrumentation context file in the project's .amplitude folder come first and override everything else. Next come the events and properties seen through the Amplitude MCP server, then the real tracking call sites in the codebase, and last the taxonomy skill, which holds Amplitude's general naming standards. The skill starts by reading the repository's instrumentation context. It is used before a team adds new events, so that the new code looks like the existing code. It is part of the amplitude mcp-marketplace repository and is added to a compatible agent with the skills command. Its security audits passed with Gen Agent Trust Hub, Socket and Snyk.…
Highlights
- Finds real tracking call patterns in the code
- Documents SDK calls, signatures and imports
- Naming conventions from a strict source order
- Honours a customer instrumentation context file
Ratings & Reviews
No ratings yet
Be the first to rate discover-analytics-patterns.
People also visit
add-analytics-instrumentation
End-to-end analytics instrumentation workflow for a PR, branch, file, directory
discover-analytics-patterns FAQ
What does discover-analytics-patterns do?
It finds out how the codebase writes its analytics tracking calls, so new events follow the same patterns.
Which conventions win?
Customer directives in the instrumentation context file come first, then events seen through the Amplitude MCP server, then real call sites, and last the taxonomy skill.
What is the instrumentation context file?
A file in the project's .amplitude folder, with conventions the customer wants followed, and any files it references.
How do I install it?
Run: npx skills add https://github.com/amplitude/mcp-marketplace --skill discover-analytics-patterns
What security audits has it passed?
Gen Agent Trust Hub, Socket and Snyk all passed.
What are the best discover-analytics-patterns alternatives?
Popular alternatives to discover-analytics-patterns include add-analytics-instrumentation, diff-intake and discover-event-surfaces. See all discover-analytics-patterns alternatives