signals-scout-session-replay

Detects session replay capture cliffs and friction clusters in PostHog analytics data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session replay silently breaks in two ways: recordings stop being captured while site traffic continues (a capture cliff that permanently loses data), and user friction like rage clicks or errors-after-interaction concentrates on specific pages without anyone noticing. This Skill continuously monitors PostHog session replay data to catch both failure modes and files corroborated, actionable reports.

Core Features & Use Cases

  • Capture cliff detection: Compares daily recording volume against site traffic to spot unexplained drops, then diagnoses the cause via Team config activity logs and SDK health properties like $replay_sample_rate.
  • Friction concentration analysis: Finds URLs and elements where rage clicks, dead clicks, or errors-after-click spike above their own historical baseline, corroborated with heatmaps and watchable example recordings.
  • Replay vision scanner monitoring: Aggregates LLM scanner observations across sessions and detects watch gaps where scanners silently stop producing observations.
  • Use Case: A PostHog user's checkout page suddenly shows rage clicks jumping from 9/day to 110/day across 23 users. The scout identifies the 'Pay now' button as the friction point, links example recordings, and files a P2 report routed to the checkout owner.

Quick Start

Ask the agent to run a session replay scout pass to check whether recordings are still being captured and whether any pages show concentrated rage-click friction.

Frequently Asked Questions about signals-scout-session-replay

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

FAQPage Schema
How do I detect when session replay stops recording in PostHog?

Compare daily recorded session counts from raw_session_replay_events against daily event sessions from the events table. A capture ratio dropping below roughly 40% of its 14-day norm while traffic holds steady indicates a capture cliff worth investigating.

How to find rage click hotspots on specific pages?

Group $rageclick events by host and ID-normalized path, then compare the last 24 hours against the prior 13-day daily mean. A path running at least 3x its baseline with 10+ sessions and 5+ persons qualifies as a friction cluster.

Why does filtering session_replay_events by start_time return zero rows?

The start_time column on the friendly view is an aggregate projection, so WHERE clauses on it silently return nothing. Time-filter the raw_session_replay_events table on min_first_timestamp instead.

Does a low recording-to-traffic ratio mean replay is broken?

No. Sampling rates, minimum durations, and quotas deliberately suppress recordings, so a low ratio is usually configuration. Only an unexplained change in the ratio over time is a signal worth reporting.

What are the limitations of session_replay_features data?

Rows exist only for recorded sessions, so absence means sampling or lag, never absence of friction. The table also has multiple rows per session until parts merge, so pre-aggregate by session_id before summing counters.