ClaudeSuperPower
SubmitLog in

debug-replay

Skill

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

30Debugging

Install

git clone https://github.com/amplitude/mcp-marketplace.git ~/.claude/skills/debug-replay

What is debug-replay?

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.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~101 tokens of context used while enabled, before you invoke anything

Trust

83/100 · Excellent

2 factors scored below maximum

Documentation

README · ~6 min read

Debug Replay

Investigate bugs by finding session replays where the error occurred, extracting the interaction timeline, and distilling it into numbered reproduction steps an engineer can follow. This skill bridges the gap between "a user reported a bug" and "here's exactly how to reproduce it."

CRITICAL: Tool Reference

This skill operates on three Amplitude Session Replay tools. Use them in this order:

  1. Amplitude:get_session_replays — Find sessions matching event filters (errors, specific users, time windows). Returns session metadata and replay links.
  2. Amplitude:list_session_replays — Simple paginated listing when you already have a user/device ID or just need recent sessions. Returns replay_id in device_id/session_id format.
  3. Amplitude:get_session_replay_events — Decode a specific replay into an interaction timeline: navigations, clicks, inputs, scrolls. Requires replay_id from the tools above.

Supporting tools used in this skill:

  • Amplitude:get_users — Look up users by email, user ID, or other identifiers.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

cardputer-buddy

Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user wants to add a new app, push a single changed .py without re-flashing, watch device serial logs, or run a one-shot REPL command. Trigger on "add

32.8K stars

planning-with-files

Persistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Claude Code, Codex, Cursor, Kiro, OpenCode and 60+ agents via the Agent Skills standard.

25.8K stars

troubleshoot

Diagnose and fix a failing or misbehaving Atomic Agents app — import errors, schema validation failures, empty or malformed LLM output, provider role/mode errors, history and context problems, MCP transport errors. Use when the user reports an error, traceback, or wrong behavior in atomic-agents cod

6.1K stars