skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

investigating-replay

Investigates PostHog session recordings by gathering metadata, person profiles, events, and linked error issues.

713|118|Updated Aug 11, 2020
Search Tags:#investigate#Debugging#error tracking#session recording#session replay#PostHog#replay vision
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill investigating-replay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigating-replay
Source: https://github.com/PostHog/posthog-foss/tree/main/products/replay/skills/investigating-replay
Command: npx skills add https://github.com/PostHog/posthog-foss --skill investigating-replay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually investigating a session recording requires chaining multiple PostHog API calls — fetching recording metadata, retrieving the person profile, querying session events, and searching error tracking issues. This Skill consolidates that entire investigation into one guided workflow so you can answer "what happened in this session?" in a single pass.

Core Features & Use Cases

  • Parallel context gathering: Fetches recording metadata, person profiles, and same-session events (pageviews, exceptions, rage clicks) via SQL queries in one coordinated flow.
  • Error tracking linkage: Extracts exception fingerprints from the session and finds matching error tracking issues with their status.
  • Replay Vision AI summaries: Optionally checks for existing AI-generated session summaries or runs a summarizer scanner on demand, including safe temporary scanner creation and cleanup.
  • Use Case: A user reports a bug and shares a session ID. Use this Skill to immediately produce a narrative covering who the user was, what pages they visited, what exceptions occurred, and which error tracking issues are linked.

Quick Start

Investigate PostHog session recording abc123 and tell me who the user was, what they did, and what errors occurred.

Frequently Asked Questions about investigating-replay

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

FAQPage Schema
How do I investigate a PostHog session recording?▼

Provide the recording or session ID and the workflow fetches recording metadata, the person profile, same-session events via SQL, and linked error tracking issues in parallel. Results are synthesized into a narrative covering who the user was, what they did, and what errors occurred.

How to find errors and exceptions in a PostHog session?▼

Query the events table filtered by session ID for $exception events, grouping by exception fingerprint, type, and message. The resulting fingerprints can then be matched against error tracking issues to get links and resolution status.

Can I get an AI summary of a PostHog session replay?▼

Yes, via Replay Vision summarizer scanners. The workflow first checks for an existing summary observation, then scans the session with an existing summarizer scanner, or creates a temporary disabled scanner with your permission for a one-off summary.

What happens if the session recording has no person profile?▼

If the recording's person field is null, the user was anonymous and person properties are unavailable. Session events, errors, and metadata can still be queried and analyzed normally.

When should I skip checking error tracking issues for a session?▼

Skip the error tracking step when the recording metadata shows a console error count of zero, since there are no exceptions to investigate. This avoids unnecessary queries for clean sessions.

Related Skills

Explore More Software Engineering Skills→
PostHogPostHog
58

user-deep-dive

Aggregate PostHog and Vitally data into a user activity profile with outreach angles.

Official
Advanced
DayoptDayopt

debug

Diagnose and resolve debugging issues using phase-based investigative workflows.

Official
Advanced
PostHogPostHog
58

configuring-experiment-analytics

Configure experiment analytics workflows for exposure, metrics, and interpretation.

Official
Advanced
timequitytimequity
6

root-cause-tracing

Trace call stacks backward to identify the original error trigger.

Official
Advanced