session-review

Triage session recordings and grade findings as MEASURED, RECONSTRUCTED, OBSERVED, or INFERRED.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/BayramAnnakov/edu-ai-product-analyst --skill session-review-bayramannakov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-review
Source: https://github.com/BayramAnnakov/edu-ai-product-analyst/tree/main/.claude/skills/session-review
Command: npx skills add https://github.com/BayramAnnakov/edu-ai-product-analyst --skill session-review-bayramannakov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Session recordings are persuasive but easy to misread: teams watch a few replays, generalize from anecdotes, and ship findings nobody can verify. This Skill turns a pile of recordings into a short, graded findings table where every claim carries evidence coordinates a colleague can check in two minutes. ## Core Features & Use Cases - Question-scoped triage: refuses to open a player until a decision-relevant question exists, then classifies recordings from the index so only 5-10% of the corpus gets watched. - Four-grade evidence ladder: every claim is labeled MEASURED, RECONSTRUCTED, OBSERVED, or INFERRED, with agents forbidden from awarding themselves OBSERVED. - Dead-click and rage-click gate: classifies copy-selects, reading taps, false affordances, and slow controls before citing any count as a defect. - Use Case: Given a PostHog or local replay export showing drop-off at a report page, triage 159 recordings down to a dozen candidates, fan out subagents to extract event timelines, watch the survivors, and publish a 3-5 row findings table with grades, timestamps, and owners. ## Quick Start Ask the assistant to review the session recordings in this folder and produce a graded findings table explaining why users drop off before generating a report.

Frequently Asked Questions about session-review

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

FAQPage Schema
How do I analyze session recordings to find why users drop off?

Start with a question whose answers would change a decision, then triage recordings from the index by duration, clicks, and furthest step rather than watching everything. Watch only the 5-10% that survive triage and grade every finding with evidence coordinates.

How to review session replays from PostHog or Microsoft Clarity?

The same method applies across PostHog, Clarity, Hotjar, Smartlook, and Yandex Webvisor; only the column names and export paths differ. PostHog lists recordings via API but requires manual JSON export for snapshots, while Clarity offers only aggregate exports.

Are dead clicks in session recordings always usability defects?

No. Dead clicks cover at least four behaviors: copy-selects, reading taps, false affordances, and slow controls. Classify each cluster before citing it, and confirm a false affordance in source code by checking the element has no event handler.

Can an AI agent grade session replay findings as observed?

No. OBSERVED means a human watched the replay play, and agents must write OBSERVED - PENDING with coordinates for a person to clear. Agent output from event logs, snapshots, or headless renders is graded RECONSTRUCTED or MEASURED at best.

What are the privacy risks of sending session recordings to an AI model?

Replay DOM contains real user data like names, emails, and invoice numbers. Serve replays only on localhost, send synthetic or lab data to agents freely, and share coordinates rather than screens between people unless your organization approved the data path.