User Cohort Forensics
Investigates individual users and user populations in Amplitude — resolve users by email/ID, read profiles, batch-analyze event timelines, spot-check cohort membership. Use for "what did user X do", attribution audits, population sampling, and email-to-user-ID resolution.
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 user-cohort-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/user-cohort-forensics ~/.claude/skills/user-cohort-forensicsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# User & Cohort Forensics ## The arcs **Single user deep-dive:** `get_amp_user_data` `include: 'id'` (resolve the user: email, user ID, device ID, or amplitude ID) → `include: 'profile'` (lifecycle, acquisition, usage stats) → `include: 'timeline'` (session-aware event history). `include: 'both'` gets profile + timeline in one call when you know you'll need both. Summarize journeys; don't dump raw events. **Population analysis (batched):** build the user set first (`query_amplitude_data` with a user-ID group_by to rank by volume, or `use_amplitude_cohorts` `action: 'find'` for a filtered set) → `get_amp_user_data` `include: 'timeline'` in parallel batches — up to 10 identifiers per call, 10–20 calls in flight is normal for population analysis; hundreds of calls total is fine. Keep each call narrow (event types, window) so responses stay small. **Cohort spot-check:** prefer existing cohorts — `use_amplitude_cohorts` `action: 'list'` or `action: 'get'` before building ad hoc definitions. `action: 'membership'` verifies specific users. Check a member's timeline for the exact markers (purchase, typing, checkout events) rather than trusting the cohort definition blindly. **Email → ID resolution:** `get_amp_user_data` `include: 'id'` per email; uploaded email lists are resolved in batches of ≤10 identifiers per call. For bulk exports, batch and note the retry pattern on individual failures. ## Parameterization notes
Details
- Skill name
user-cohort-forensics- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude/skills/user-cohort-forensics/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the User Cohort Forensics skill do?
Investigates individual users and user populations in Amplitude — resolve users by email/ID, read profiles, batch-analyze event timelines, spot-check cohort membership. Use for "what did user X do", attribution audits, population sampling, and email-to-user-ID resolution.
How do I install the User Cohort 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 User Cohort 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.
Dataverse
52korchard333/claude-power-platform-community
Dataverse Schema and Data Modeling. Use when: designing tables, columns, relationships, alternate keys, security roles, cascade behaviors, elastic tables, virtual tables, Dataverse search, query patterns (OData/FetchXML), naming conventions.
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.
Security
52korchard333/claude-power-platform-community
Dataverse Security Model. Use when: designing security roles, column-level security, business units, teams (owner/access/AAD group), record sharing, hierarchy security, minimum viable privileges, security role management via Web API.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.