Discover Analytics Patterns skill for Claude Code: find how your repo sends events

Amplitude's skill that makes Claude map how your codebase sends analytics events, so new tracking code matches the old.

Installs: 48.8K; on skills.sh
Stars: 46; on GitHub
Updated: Oct 2026; last repo commit

discover-analytics-patterns makes Claude search your repo for the real tracking calls: SDK calls, typed Ampli methods, custom wrappers and hooks. It lists each pattern with a generalized example and the files where it appears. It also reports the dominant event and property naming styles, so new events look like the old ones.

It starts by reading .amplitude/instrumentation-agent-context.md if your repo has one. If the Amplitude MCP server is connected, it samples event and property names from your project. If not, it falls back to searching the code. For naming it can fall back to the taxonomy skill, so install that one with it.

Good for

Engineers adding analytics events who want them to match the existing style
Teams on Amplitude who ask "how do we track events here?"
Anyone running Amplitude's discover-event-surfaces or instrument-events skills, which call this one

Install discover-analytics-patterns

Claude Code

Copy this prompt.

Install the discover-analytics-patterns skill in Claude Code. Run this command:

claude plugin install amplitude

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

The plugin route installs every skill in the Amplitude plugin and the Amplitude MCP server from its .mcp.json (https://mcp.amplitude.com/mcp). In Claude Code the README tells you to authenticate when prompted. The skills CLI route is listed with taxonomy because this skill reads it or hands off to it. The skills CLI route copies the skill folders. For the Amplitude MCP server, use the plugin route or add https://mcp.amplitude.com/mcp to your client yourself.

From the project README. Source.

What's in the skill

When it loads

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.

Sections in SKILL.md

Step 0: Read repo instrumentation context
Step 1: Find tracking calls
If the Amplitude MCP is connected
If the Amplitude MCP is not available (fallback)
Step 2: Group by pattern
Step 3: Resolve naming conventions
Step 4: Output
Pattern: <short descriptive name>
Step 5: Handle no results

Key facts

Author: Amplitude, Inc. (vendor's own repo; LICENSE names Amplitude, Inc. as copyright holder, README calls it the official Amplitude plugin)
License: MIT (LICENSE and README)
Installs on skills.sh: 48,765 as of Nov 2, 2026
GitHub stars: 46 for the amplitude/mcp-marketplace repo, Nov 2, 2026
What is inside: 1 file: SKILL.md (the git tree lists nothing else in the folder)
Part of: The amplitude plugin (plugins/amplitude), version 1.7.0 in the marketplace manifest
Last commit to the repo: Oct 31, 2026
Needs: An Amplitude account with API access and an MCP-compatible client (README Requirements)
Works in: Claude Code, Cursor, Codex, Gemini CLI and Claude (README)

What it includes

Reads .amplitude/instrumentation-agent-context.md if it exists
Looks for the file at the repo root or the subfolder you are working in. Rules in it count as customer directives and beat anything the skill infers.
Files · Step 0: read repo context
Samples events from the Amplitude MCP, or searches the code
With the Amplitude MCP connected it reads sample event and property names, then searches the code for them. Without it, it searches for patterns such as .track(, ampli., amplitude.track and amplitude.logEvent, plus import lines and custom wrappers.
Files · Step 1: find tracking calls
Groups call sites by library, method and argument shape
Two calls are the same pattern only if library, method name and argument structure match. A custom wrapper counts as its own pattern, noted with what it wraps.
Read · Step 2: group by pattern
Picks event and property naming by a fixed order
Order: the repo context file, then events seen via the Amplitude MCP, then real call sites in the code, then the taxonomy skill. If still unclear it says so.
Read · Step 3: resolve naming conventions
Prints two naming conventions and a list of patterns
Prints event_naming_convention and property_naming_convention, then each pattern with a description, a generalized example and relevant file paths, most common first.
Try: “How do we track events in this repo?”
Read · Step 4: output
Says so when no tracking calls are found
Suggests checking whether Amplitude or another analytics library is set up and offers to search for Segment, Mixpanel or PostHog.
Read · Step 5: handle no results

From the official docs

Permissions

Medium risk

This skill reads your code and your Amplitude project and bundles no scripts. The plugin route adds an Amplitude MCP server, so check the project you sign in to.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Event names from your project enter the chat
Event and property names read from Amplitude become part of the conversation with your AI provider. Check that your naming is not sensitive before using it on a shared account. github.com
The plugin route adds an Amplitude MCP server
The amplitude plugin ships a .mcp.json that points Claude at https://mcp.amplitude.com/mcp. You sign in to Amplitude when prompted, and the skill can then read from that project. github.com
The plugin route installs every Amplitude skill
The repo has 36 skill folders in the plugin, while the README lists 27. Use the skills CLI route in the install box if you want only the ones this page names. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	SKILL.md names no read-only setting.
Talks to	mcp.amplitude.com (the Amplitude MCP server from the plugin .mcp.json)
Sign-in and keys	Signs in to Amplitude through the MCP server when you are prompted; the README does not say where the sign-in is stored.
Scopes	Searches your repo for analytics calls and import lines Reads sample event and property names from your Amplitude project through the MCP server

Questions

What does the discover-analytics-patterns skill do?

It makes Claude find how your codebase sends analytics events. The result lists each tracking pattern with an example and the files that use it, plus the naming style for events and properties. It is meant to run before new tracking code is written.

How do I install it?

Use the install box above. The plugin route installs the whole Amplitude plugin. If you use the skills CLI route, install taxonomy with it, because this skill falls back to ../taxonomy/SKILL.md for naming. The repo has 36 skill folders in the plugin, while the README lists 27.

Is it official?

Yes, it is in the vendor's own repo. The amplitude/mcp-marketplace README calls the plugin the official Amplitude plugin for AI coding tools, and the LICENSE names Amplitude, Inc. as the copyright holder.

Does it need an Amplitude account or API key?

Only for the MCP part. The README lists an Amplitude account with API access as a requirement for the plugin. The skill itself says that without the Amplitude MCP it searches the codebase instead.

Is discover-analytics-patterns safe to run?

It bundles no scripts. SKILL.md tells Claude to search your code and read sample names from Amplitude, and does not mention editing files. The plugin route also adds an Amplitude MCP server, so read the permissions section before you sign in. Our advice: run it first on a repo you can open in a clean git state, so you can see if anything changed.

How is it different from add-analytics-instrumentation?

This skill only maps existing tracking style. The README describes add-analytics-instrumentation as an end-to-end workflow that reads code, decides what to track and produces a full plan in one pass. The README says a typical flow is diff-intake, discover-event-surfaces, instrument-events, with this skill keeping new tracking in line with existing conventions.

Does it work in Cursor, Codex or Gemini CLI?

The README says the Amplitude plugin works with Claude Code, Cursor, Codex, Gemini CLI and Claude, and gives an install route for each except Claude. See the tabs in the install box.

Information

updated Nov 2, 2026

Repository: amplitude/mcp-marketplace
Folder: plugins/amplitude/skills/discover-analytics-patterns

amplitude/mcp-marketplace skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5

amplitude/mcp-marketplace README · github.com
marketplace.json · github.com
discover-analytics-patterns SKILL.md · github.com
skills.sh listing · skills.sh
LICENSE · github.com