# 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.

- Skill: `builderio/replay-triage` (Agent Skill)
- Install (CLI): `npx get-skill add builderio/replay-triage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/builderio/replay-triage/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: Builder.io (https://skillmd.com/u/builderio)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/builderio/replay-triage

---


# 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.

