discover-analytics-patterns
Analyticsamplitude/mcp-marketplaceskills.sh ↗
Installs
6,942
deduplicated, at the last sync
Since we started
+46.5%
40 readings, about 2 hours apart. Not a live curve.
Our category
Analytics
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill analyzes a codebase to determine how analytics events are tracked using specific code patterns. It identifies the concrete SDK calls, function signatures, and import methods used for sending events within the project.
- deduplicated list of tracking patterns
- generalized examples of tracking calls
- file paths where each pattern appears
- dominant event and property naming conventions
- codebase repository access
not detected
The evidence does not provide any information regarding paid services, APIs, or credentials.
not detected
The evidence does not mention any required registration process for using the skill.
It cannot determine which events exist in the project; it only finds patterns of how tracking calls are made. It also cannot verify or decide on the correct coding style to follow without explicit customer directives, MCP data, or codebase inference.
Evidenceplugins/amplitude/skills/discover-analytics-patterns/SKILL.md:1-208
--- name: discover-analytics-patterns description: > Discovers how analytics tracking calls are actually written in this codebase — the concrete SDK calls, function signatures, and import patterns used to send events. Use this skill whenever you need to understand the existing analytics instrumentation patterns before adding new tracking, when someone asks "how do we track events here?", "show me the analytics setup", "what's the analytics pattern in this codebase?", or any time the instrument-events or discover-event-surfaces skills are about to run and you need to know the correct coding style to follow. Outputs a deduplicated list of patterns with generalized examples and the file paths where each pattern appears, plus the dominant event and property naming conventions inferred from those call sites. Always use this skill before writing any analytics instrumentation code. --- # discover-analytics-patterns Your goal is to find out **how** this codebase sends analytics events — not which events exist, but the specific code patterns engineers use to fire a tracking call. This output helps engineers add new events that look consistent with the rest of the cod
Read 1 of 1 text files in the skill.
Installfrom the directory
npx skills add https://github.com/amplitude/mcp-marketplaceInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
1 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 4.7k, not zero — the range is 4.7k to 6.9k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
This skill analyzes your codebase to identify all concrete patterns used for tracking events. It tells you the specific SDK calls and function signatures so you know how to write new, consistent instrumentation.
The provided evidence does not contain any information about paid services or costs associated with using the skill.