Skip to content

BuilderIO/agent-native / templates/analytics/.agents/skills/replay-triage

replay-triage

Verified

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

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.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall