What problem does it solve? Determining whether a specific Ray-Ban Meta or Meta glasses product actually supports a given DAT iOS, DAT Android, Display, or Web Apps capability is error-prone because marketing labels, firmware versions, and SDK releases drift apart. This Skill replaces guesswork with a versioned, evidence-backed compatibility tuple so teams never ship support claims based on product names or assumptions. ## Core Features & Use Cases - Versioned compatibility tuples: Records phone OS, Meta AI companion version, glasses firmware, on-glasses DAT app, link transport, and observed DeviceType as one auditable unit. - Machine-checked evidence packets: Ships a YAML evidence-packet template and a validator script that enforces all eight COMP-* evidence rows, redaction rules, and Gen 3 gating before a claim is closed. - Strict anti-hallucination boundaries: Blocks mapping Gen 3 labels to SDK enums, treating login-gated pages as known values, or equating iOS, Android, and Web Apps symbols by name. - Use Case: Before promising camera support on Ray-Ban Meta Gen 2 with DAT 0.9, run the workflow to freeze the exact artifact, read the authenticated version-dependency table, exercise the capability on the physical pair, and produce a validated compatibility packet. ## Quick Start Ask the agent to verify whether a named Meta wearable supports a specific DAT capability and produce a validated compatibility evidence packet.
