meta-wearables-developer-operations

Audit and operate Meta Wearables Developer Center projects, release channels, testers, and telemetry.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-wearables-developer-operations-shotcowboystyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-wearables-developer-operations
Source: https://github.com/shotcowboystyle/meta-wearables-ops-plugin/tree/main/.agent/skills/meta-wearables-developer-operations
Command: npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-wearables-developer-operations-shotcowboystyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing the Meta Wearables Developer Center lifecycle involves many distinct identity systems, release channels, and evidence levels that are easy to confuse, leading to unverified releases, leaked credentials, or false claims about tester access and device capability. ## Core Features & Use Cases - Account and Project Auditing: Resolve MMA organizations, Wearables teams, operator roles, projects, and platform app identities while keeping secrets redacted. - Release Channel Operations: Map versions, channels, tester invitations, and Meta AI app state while separating Developer Mode from signed distribution. - Telemetry and Privacy Review: Audit telemetry categories, opt-out configuration, disclosure, retention, and deletion separately from product privacy. - Use Case: When preparing a DAT iOS and Android app for a private Ray-Ban Display test channel, use this Skill to verify organization access, record permission justifications, invite a tester, and produce an evidence packet with DCO-* IDs. ## Quick Start Audit my Meta Wearables Developer Center project configuration and release channel state for the DAT iOS app and report which evidence items are access-gated.

Frequently Asked Questions about meta-wearables-developer-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a release channel in Meta Wearables Developer Center?

Release channel setup requires resolving your project, platform app identity, and a version with a Ready DAT build, then assigning one version per channel and inviting testers. This Skill walks through the workflow and records evidence for each step.

What is the difference between a Managed Meta Account organization and a tester Meta Account?

An MMA organization holds company-level membership and admin control, while a tester Meta Account is a separate identity used to receive release invitations. The Skill preserves both identity systems and never treats one as proof of the other.

Does Developer Mode prove my Meta glasses app is ready for release?

No. Developer Mode is a local development path and does not prove attestation, channel membership, signed distribution, or production readiness. The Skill keeps Developer Mode evidence separate from signed release-channel evidence.

Can this Skill delete a project or switch a release channel automatically?

No. Destructive operations like project deletion, tester revocation, channel switching, and version publication require explicit user authorization, a resolved target, and pre/post action receipts. The Skill stops rather than acting on stale screenshots or documentation.

How do I audit telemetry and privacy for a Meta Wearables DAT app?

Telemetry audit lists collected operational categories, opt-out configuration, disclosure, retention, and deletion policies separately from product privacy review. Opt-out alone is not treated as a complete privacy program.