What problem does it solve? Verification suites pass even when they are structurally blind to the change being tested, producing false confidence. This Skill decides which verification tier — host tests, simulator, or physical television — can actually see a given change, and names the tiers that cannot. ## Core Features & Use Cases - Tier Routing: Maps what a change touched (pure logic, UI layout, text rasterization, animation, frame rate, player pipeline, FFI, release configuration, packaging) to the cheapest tier capable of verifying it. - Blind-Spot Analysis: Documents what each tier structurally cannot detect, such as the fps tier's blindness to pixels and the synthetic test tier's bypass of the Plex metadata-to-plan pipeline. - Handoff to Executors: Ends by delegating to execution skills like ui-sim, tv-session, tv-lock, fleet-plan, profile-tv, crash-triage, or cut-release. - Use Case: After editing an icon's geometry in a Rust TV app, ask which suite to run — the Skill routes you to a device capture looked at by eye, not the fps suite that cannot see pixels. ## Quick Start Ask which verification tier is needed for your change, describing what files or behavior you modified.