What problem does it solve?
Creating a Replay Vision scanner without checking its projected spend can drain an organization's credit budget within the first few scheduled sweeps, since scanners run automatically every 5 minutes against all matching recordings. This Skill guides agents through choosing the right scanner type, shaping the session query, estimating monthly credit spend, and checking remaining budget before creating or widening a scanner.
Core Features & Use Cases
- Scanner type selection: Configure monitor, classifier, scorer, or summarizer scanners with the correct scanner_config shape, knowing the type is locked after creation.
- Cost estimation and budget gating: Call vision-scanners-estimate-create and vision-quota-retrieve, prorate the monthly projection against the remaining billing period, and confirm with the user before creating an expensive scanner.
- Query and sampling tuning: Narrow the RecordingsQuery and adjust sampling_mode, sampling_rate, and model tier to control spend per observation.
- Use Case: A user asks to flag rage-click sessions automatically. The Skill builds a monitor scanner on the $rageclick event, estimates it at 2,000 credits/month against 800 remaining, surfaces the numbers, and suggests a focused sampling_mode or a per-scanner credit_limit before creating.
Quick Start
Ask the agent to create a Replay Vision scanner that watches sessions matching your criteria and have it estimate the monthly credit cost and check the remaining budget before creating it.