finding-replay-for-issue

Ranks session recordings linked to an error tracking issue and selects the most informative replay.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill finding-replay-for-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-replay-for-issue
Source: https://github.com/PostHog/posthog-foss/tree/main/products/replay/skills/finding-replay-for-issue
Command: npx skills add https://github.com/PostHog/posthog-foss --skill finding-replay-for-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Error tracking issues in PostHog can have hundreds of linked session recordings, most of which are crash-only fragments or duplicates. Manually picking a useful replay from that list is slow and often yields sessions with no pre-error context.

Core Features & Use Cases

  • Candidate discovery: Queries exception events by issue fingerprint to collect up to 20 recent session IDs where the error occurred.
  • Quality-based ranking: Filters out sessions under 10 seconds or over 1 hour, then ranks by duration sweet spot (2-15 minutes), active time ratio, activity score, and recency.
  • Contextual presentation: Returns the best recording with a watch link, pre-error page journey, and error frequency for that session.
  • Optional AI summary: Uses Replay Vision summarizer scanners (check-then-scan) to generate a narrative summary of the selected session.
  • Use Case: A developer sees a spike in an error tracking issue and asks for a replay; the skill returns the single most informative recording showing what the user did before the exception.

Quick Start

Find the most informative session replay for error tracking issue <issue_id> and summarize what the user was doing before the error.

Frequently Asked Questions about finding-replay-for-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a session replay for a PostHog error tracking issue?

Provide the issue ID, and the skill queries exception events matching the issue fingerprint to find linked session IDs, then ranks candidates and returns the best recording with a watch link and pre-error context.

How are linked session recordings ranked for an error issue?

Sessions under 10 seconds or over 1 hour are filtered out first. Remaining candidates are ranked by duration sweet spot (2-15 minutes), active time ratio above 0.3, activity score, and recency.

Can I get an AI summary of a session replay instead of watching it?

Yes, via Replay Vision. The skill checks for an existing summarizer observation on the session, and if none exists, finds a summarizer scanner and runs an asynchronous scan, polling until it succeeds.

Why do some exception events have no linked session recording?

If $session_id is null on many exception events, session replay may not be enabled for the affected users. The skill flags this as a possible coverage gap when it occurs.

What if all linked sessions for an error are very short?

If all candidates are under 10 seconds, the error likely crashes the page immediately. The skill reports this as useful diagnostic context even when no long replay is available.