Discover Event Surfaces

Point this at a change_brief YAML from diff-intake and it'll produce a candidate list of analytics events to instrument, organized into business outcomes, user journey transitions, feature success moments, and friction or failure points. The useful part is that it traces the actual user flow through the code (entry points, async boundaries, terminal states) before proposing anything, so the events map to real funnel steps rather than button clicks. It also pulls the project's existing Amplitude taxonomy and drops anything that duplicates a tracked event, including semantic duplicates like proposing "Plan Upgraded" when "Subscription Upgraded" already exists. The output is deliberately broad, so expect a long list that a PM still has to prune. It is step 2 of a three-part workflow and depends on the diff-intake and discover-analytics-patterns skills being present.

skills.sh installs: 55.5K
GitHub stars: 47
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add amplitude/mcp-marketplace --skill discover-event-surfaces --agent claude-code

Installs into .claude/skills of the current project.

Files

discover-event-surfaces

You are step 2 of the analytics instrumentation workflow. Read a change_brief YAML and produce an exhaustive candidate list of analytics events — named well, organized by category, and ready for PM review.

Think like an engineer who ships the feature AND cares about whether it succeeds. Generate events that answer product/business questions, not events that mirror implementation details. Aim for breadth and quality — a downstream skill will narrow the list.

Read the taxonomy skill at ../taxonomy/SKILL.md to understand core analytics philosophy and naming standards.

1. Parse the change_brief

classification.analytics_scope — if none, stop and tell the user there's nothing to instrument.
summary — one-line description of the change.
user_facing_changes — primary signal. Each entry = something a user can now do or see differently.
surfaces.components — modified UI components; where interactions happen.
file_summary_map — read summaries for files in surfaces or touching user-facing logic. Skip tests/config/tooling.