What problem does it solve? Requests like "use the full Meta Wearables SDK" or "support Gen 2 and Gen 3" often hide unverified modules, stale upstream examples, unsupported device claims, and missing physical-device evidence. This Skill audits such requests against the actual public iOS, Android, and Web Apps SDK surface before implementation begins. ## Core Features & Use Cases - Full-surface capability audit: Maps every requested capability (camera, audio, Display, sensors, sessions, registration, release) to exact iOS MWDAT modules and Android Maven artifacts with source-pinned status. - Terminology and device-generation resolution: Resolves ambiguous phrases like "regular SDK" and keeps "Gen 3" as an unresolved alias until official mapping and named-device evidence exist. - Evidence-level enforcement: Separates source, static, build, mock, browser-sim, connected, physical, signed, and release-channel proof so mock or compile results are never reported as physical proof. - Use Case: A product team asks for one app covering Ray-Ban Meta Gen 2, Gen 3, and Ray-Ban Display with camera, microphone, and Web Apps parity. The audit returns the exact module matrix, source conflicts, privacy paths, and missing evidence rows instead of an unqualified "full SDK" claim. ## Quick Start Ask the agent to audit whether a Meta Wearables request covering iOS, Android, and Display actually uses the full public SDK surface with proper evidence.
