Menu

Individual skill

replay-triage

Review outcome-ranked first-touch sessions and their replay evidence. Use when radar checks or the weekly report identify a first-session failure.

templates/analytics/.agents/skills/replay-triage/SKILL.md

Read pinned source

Source commit ff01b4009091c2140edb34d6f790ec64e7823356

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
7,644
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Replay triage

- Run `pnpm --filter analytics radar:triage` or pass `--date YYYY-MM-DD` for a
  UTC day.
- Start with `prompted_no_output`, `recording_started_no_ready_clip`, and
  `onboarding_abandoned`. Friction and performance fields explain outcomes; do
  not rank sessions by friction score.
- Review at most the top 15–30 sessions. When a bearer is available, fetch replay
  timelines only for those recording ids through Analytics' deployed action.
- Use event names, offsets, counts, trouble labels, and performance summaries.
  Never include emails, prompt text, URLs, or other user content in a report.