Debug Replay
by amplitude96fc7d4c58bbNo license42 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Turns bug reports into reproducible steps by finding error sessions in Amplitude Session Replay, extracting interaction timelines, and identifying the common action sequence that precedes the failure. Use when a user reports a bug, an error event spikes, someone says "how do I reproduce this", "what happened to user X", "repro steps", or you need to understand what a user did before an error occurred.
Only the file list is public. File contents are available once the skill is installed in a workspace.
| Path | Size | Type |
|---|---|---|
| SKILL.md | 9.8 KB | text/markdown |
Source and attribution
Source:amplitude/mcp-marketplaceinplugins/amplitude/skills/debug-replayat commit96fc7d4
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from amplitude/mcp-marketplace
What Would Lenny Do
amplitude
Answers product strategy, growth, pricing, hiring and leadership questions by searching Lenny Rachitsky's archive and synthesizing a recommendation.
Weekly Brief
amplitude
Produces a weekly Amplitude analytics briefing covering trends, wins, risks, and next-week priorities.
User Cohort Forensics
amplitude
Investigates individual users and user populations in Amplitude, resolving identities, reading profiles and analyzing event timelines.
Use Amp Guides Surveys
amplitude
Lists Amplitude Guides and Surveys or reads one item's full configuration via the use_amp_guides_surveys tool.
Taxonomy
amplitude
Reference guidance for Amplitude event taxonomy: naming standards, data quality auditing, scoring, and safe deprecation.
Scheduled Report Refresh
amplitude
Refreshes recurring reports (daily briefings, WBRs, experiment briefs) from saved Amplitude content — fetch the dashboard, re-pull its charts, fill gaps with ad hoc queries, summarize deltas. Use for "run the daily/weekly report", "refresh this dashboard's numbers", or scheduled custom-agent report runs.
More in Software Development
Writing Plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
Verification Before Completion
obra
Forces running fresh verification commands and reading their output before claiming work is complete, fixed, or passing.
Using Git Worktrees
obra
Sets up an isolated git worktree workspace for feature work, then runs project setup and baseline tests.
Requesting Code Review
obra
Dispatches a code reviewer subagent with crafted context to catch issues before they cascade.
Receiving Code Review
obra
Guides agents receiving code review feedback: verify suggestions, clarify unclear items, push back with technical reasoning, implement fixes one at a time.
Finishing A Development Branch
obra
Guides an agent through finishing a completed development branch: verify tests, choose merge, PR or keep, then clean up.