finding-sessions-to-watch

Filters PostHog session recordings into a shortlist of high-signal replays matching a user goal.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session replay libraries contain thousands of recordings, and an unfiltered list buries the useful sessions in noise. This Skill turns a vague intent like "why are signups dropping?" into a focused recordings query and returns a short list of sessions actually worth watching.

Core Features & Use Cases

  • Goal-based filtering: Maps user goals (signup friction, rageclicks, errors, feature usage, mobile issues, specific people or cohorts) to concrete recording filters such as visited_page, console_error_count, feature flags, and device properties.
  • Two-step event search: Collects session IDs via SQL for sessions where a specific event fired, then fetches those recordings, since the recordings query cannot filter by event name directly.
  • Triaged shortlist with deep links: Presents 3-5 promising recordings with reasons and direct replay URLs, and can save the filter as a saved filter view.
  • Use Case: A product manager asks "show me sessions where users struggled on the pricing page." The Skill confirms the real page path, queries recordings filtered by that path ordered by activity, and returns the five most telling sessions with links.

Quick Start

Ask the assistant to find session recordings of users who rageclicked or hit errors during checkout in the last week.

Frequently Asked Questions about finding-sessions-to-watch

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

FAQPage Schema
How do I find session recordings for a specific page in PostHog?

Use the recordings query with a visited_page filter, for example key visited_page with operator icontains and value /pricing. Confirm the real page path with the data schema first, then order by activity_score or console_error_count to surface the most useful sessions.

How do I find sessions where a specific event happened?

The recordings query filters by event properties, not event names, so use a two-step approach. Run SQL to collect distinct $session_id values where the event fired, then pass those IDs as session_ids to the recordings query with a matching date range.

Can I filter session recordings by feature flag or cohort?

Yes. Use a flag filter with operator flag_evaluates_to and the variant value for feature flags, or a cohort filter after resolving the cohort name to an ID with the cohorts list tool. Person properties like email also work for targeting specific users.

Why does my session recording query return zero results?

Over-filtering is the most common cause, so widen the date range or remove filters before concluding there is no data. Also verify the event names and property values exist via the data schema, and check that the date_from window matches any SQL step used to collect session IDs.

When should I not use this session discovery workflow?

Do not use it when you already have a specific recording or session ID, since that goes directly to replay investigation. It also does not apply when you need the replay for a known error issue, which uses a dedicated issue-to-replay flow.