Discover Opportunities

Discovers product opportunities by analyzing Amplitude analytics, experiments, session replays, and customer feedback. Synthesizes evidence into prioritized, actionable opportunities with RICE scoring. Use when the user asks to "find opportunities", "what should we build", "where are we losing users", "product gaps", or wants a data-driven backlog of improvements.

48 stars 12 forksData & Analytics Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add amplitude/mcp-marketplace

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add amplitude/mcp-marketplace --skill discover-opportunities
Manual install
git clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude/skills/discover-opportunities ~/.claude/skills/discover-opportunities

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Discover Product Opportunities

You are a product analytics investigator that discovers high-impact opportunities by systematically mining an Amplitude instance for signals — dropping funnels, stalled features, user friction, feedback themes, and experiment learnings. Your output is a prioritized set of opportunities, each grounded in multi-source evidence, scored for ROI, and specific enough to act on.

## Instructions

### Phase 1: Understand the Product and Scope

Before investigating, build context about the product and what matters.

1. **Bootstrap context.** Call `get_amplitude_context` to get the user's org, projects, and recent activity. Then call `get_amplitude_context` with `projectId` for the target project's settings (timezone, session definition, AI context). The AI context field often contains business context, key metrics, and product terminology — read it carefully.

2. **Discover what exists (2 parallel searches).**

   **Search A — Org-level signal.** `search_amp_entities` with `isOfficial: true`, `sortOrder: "viewCount"`, `limitPerQuery: 15`. Don't filter `entityTypes` — surface the org's most important content regardless of type. Official dashboards and charts reveal what the org tracks and values.

   **Search B — Recent activity.** `search_amp_entities` with `sortOrder: "lastModified"`, `limitPerQuery: 15`, no `entityTypes` filter. This surfaces what's actively being worked on and investigated.
Read the full skill on GitHub

Details

Skill name
discover-opportunities
Path
plugins/amplitude/skills/discover-opportunities/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Discover Opportunities skill do?

Discovers product opportunities by analyzing Amplitude analytics, experiments, session replays, and customer feedback. Synthesizes evidence into prioritized, actionable opportunities with RICE scoring. Use when the user asks to "find opportunities", "what should we build", "where are we losing users", "product gaps", or wants a data-driven backlog of improvements.

How do I install the Discover Opportunities skill?

Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Discover Opportunities popular?

It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.

Related skills

Add Analytics Instrumentation

48

amplitude/mcp-marketplace

End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature

Data & Analytics12

Analyze Account Health

48

amplitude/mcp-marketplace

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

Marketing, Sales & Business12

Analyze AI Topics

48

amplitude/mcp-marketplace

Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.

AI, LLMs & Agents12

Instrument Events

48

amplitude/mcp-marketplace

Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate t

Data & Analytics12

Discover Event Surfaces

48

amplitude/mcp-marketplace

Given a change_brief YAML (output from diff-intake), generates an exhaustive list of candidate analytics events to instrument. Takes the perspective of an engineer with a PM mindset — surfaces everything worth considering so a PM can decide what actually matters. Use this as step 2 of the analytics instrumentation workflow, immediately after diff-intake produces a change_brief. Trigger whenever a user has a change_brief YAML and wants to know what analytics events to add, or asks "what should I track for this PR", "what events should I instrument", "generate event candidates", or any request t

Data & Analytics12

Reskill

45

Azure-Samples/agent-skills-dotnet-demo

Team-wide charter and history optimization through skill extraction

Data & Analytics11

Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.