Live Data Forensics
Investigates live product issues against Amplitude data — "is X firing today", "did the release break Y", "which users are affected by Z". Covers the verify-then-query loop, query_amplitude_data parameterization, and its common failure modes. Use for incident analysis, instrumentation checks, and affected-user discovery.
Install
/plugin marketplace add amplitude/mcp-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add amplitude/mcp-marketplace --skill live-data-forensicsgit 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/live-data-forensics ~/.claude/skills/live-data-forensicsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Live Data Forensics The most common multi-tool job on this MCP server: verify live event behavior, quantify impact, find affected users. Calls observed in the wild follow one arc — follow it too. ## The arc 1. **Context.** `get_amplitude_context` (no args) → again with `projectId`. Do not guess project IDs. 2. **Reuse before rebuild.** `search_amp_entities` for existing analyses of the same area — saved charts already encode correct event names and segments. 3. **Verify taxonomy before querying.** Inspect the connected catalog and use its current taxonomy reader to confirm candidate event names, status, and queryability, then read event, user, or group properties for exact names **and scope**. Never guess names—a wrong name returns a well-formed chart with empty data, which reads as "zero". 4. **Check the event is live.** `check_for_recent_event_ingestion` confirms first-seen/last-seen before you query — a silent event means the chart will be empty no matter how correct the definition is. 5. **Quantify.** `query_amplitude_data` bursts — one slice per call (by version, by reason property, by platform), not one mega-query. Prefer the typed `chart` parameter (`kind: 'segmentation'`, events + where/group_by + date_range); it compiles server-side and validation + taxonomy checks run automatically — no separate pre-flight call needed. Compare prod vs staging/UAT projects when the question is environment-specific.
Details
- Skill name
live-data-forensics- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude/skills/live-data-forensics/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Live Data Forensics skill do?
Investigates live product issues against Amplitude data — "is X firing today", "did the release break Y", "which users are affected by Z". Covers the verify-then-query loop, query_amplitude_data parameterization, and its common failure modes. Use for incident analysis, instrumentation checks, and affected-user discovery.
How do I install the Live Data Forensics 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 Live Data Forensics popular?
It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.
Related skills
Add Analytics Instrumentation
48amplitude/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
Analyze Account Health
48amplitude/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.
Analyze AI Topics
48amplitude/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.
Soc 2
33scytale-labs/GRC-Claude-Skills
Use when the user asks about SOC 2 — Trust Services Criteria (TSC), Type 1 vs Type 2, evidence collection, gap assessments, control design, auditor preparation, or readiness for a SOC 2 attestation. For SaaS and service organizations in North America and globally.
Iso 27001
33scytale-labs/GRC-Claude-Skills
Use when the user asks about ISO/IEC 27001 — Information Security Management System (ISMS), Statement of Applicability, the 93 Annex A controls (2022 revision), risk assessment and treatment, Stage 1/Stage 2 certification audits, surveillance audits, or cross-walks with SOC 2, HIPAA, or GDPR. For organizations seeking certification globally.
Tsa Cybersecurity
33scytale-labs/GRC-Claude-Skills
Use when the user asks about TSA Cybersecurity Security Directives — pipeline (SD Pipeline-2021-01, -02), rail (SD-1580/82-2022-01), aviation (SD-1542/44-22, SD-1580-21-01), the four required cybersecurity measures (network segmentation, access control, continuous monitoring, patch management), Cybersecurity Implementation Plans (CIP), Cybersecurity Assessment Plans (CAP), or TSA reporting obligations to CISA. For US owners and operators of designated critical pipelines, freight/passenger railroads, and certain airports/aircraft operators.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.