finding-replay-for-issue
Finding the best replay for an error tracking issue
When a user says "show me a replay for this error" or "find a recording for issue X", the goal isn't just any linked session — it's the one that best shows what led to the error. Popular issues can have hundreds of linked sessions, and most are crash-only fragments or duplicate occurrences. This skill picks the most useful one.
Available tools
| Tool | Purpose |
|---|---|
posthog:error-tracking-issues-retrieve |
Get issue details (fingerprint, status, volume) |
posthog:execute-sql |
Query exception events to find linked sessions |
posthog:query-session-recordings-list |
Fetch recording metadata for candidate sessions |
posthog:session-recording-get |
Get full details for the selected recording |
posthog:session-recording-summarize |
AI summary of the selected recording (optional, slow) |
Workflow
More from posthog/skills
posthog-debugger
Debug and inspect PostHog implementations on any website. Use this skill when a user wants to understand how PostHog is implemented on a page, troubleshoot tracking issues, verify configuration, check what events are being sent, or audit a PostHog setup. Works with Chrome DevTools MCP and Playwright MCP to inspect live websites.
106integration-nextjs-app-router
PostHog integration for Next.js App Router applications
102instrument-product-analytics
>-
90feature-flags-nextjs
PostHog feature flags for Next.js applications
88instrument-feature-flags
>-
86error-tracking-nextjs
PostHog error tracking for Next.js
85