What problem does it solve? Teams integrating the Meta Wearables Device Access Toolkit risk leaking client tokens, misconfiguring callback schemes, or overstating what Developer Mode and attestation actually prove. This Skill audits the full security boundary between an app, Meta AI callbacks, the Wearables Developer Center, and release channels, returning a redacted, source-grounded evidence packet. ## Core Features & Use Cases - Identity and credential audit: Classify MetaAppID, ClientToken, bundle IDs, Android application IDs, and package tokens as secret or non-secret, verifying placement without exposing values. - Callback and attestation validation: Verify owned callback schemes, reject malformed or cross-environment inputs, and separate Developer Mode results from release-channel attestation. - Bounded evidence packet: Produce SEC-* evidence rows covering source, static config, credentials, callbacks, attestation, channel, physical runs, and release outcomes. - Use Case: Before submitting a DAT Android build to a release channel, use this Skill to confirm the mwdat_client_token stays in CI secrets, the intent-filter callback scheme is app-owned, and Developer Mode results are not mistaken for attested release proof. ## Quick Start Audit my Meta Wearables DAT iOS and Android app configuration for attestation, callback, and credential-handling issues and return a redacted security evidence packet.
