skills.rest
shotcowboystyle
shotcowboystyleCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

meta-wearables-device-proof

Plan and audit reproducible preflight and evidence for Meta Wearables apps across iOS, Android, and Web targets.

Updated Sep 6, 2026
Search Tags:#ios#android#preflight#device testing#evidence audit#meta wearables#release proof
One-click install
npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-wearables-device-proof-shotcowboystyle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-wearables-device-proof
Source: https://github.com/shotcowboystyle/meta-wearables-ops-plugin/tree/main/.agent/skills/meta-wearables-device-proof
Command: npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-wearables-device-proof-shotcowboystyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? It prevents simulated, mock, or build-level results from being mistaken for physical Meta glasses, camera, audio, Display, input, or release proof by enforcing a strict evidence ladder and redacted preflight receipts. ## Core Features & Use Cases - Target-surface inspection: Scan a workspace to classify iOS, Android, and Web App targets as TARGETS_PRESENT, TARGETS_PARTIAL, or NO_TARGET before any preflight work. - Redacted preflight receipts: Run bundled iOS and Android runners that inventory schemes, Package.resolved pins, Gradle modules, DAT artifacts, manifest keys, and toolchain signals without printing credentials or raw build output. - Evidence ladder enforcement: Separate source, static, build, mock, browser-simulator, connected, physical, signed, and release-channel evidence with stable task IDs (PRE-, MOCK-, DAT-, REL-) and explicit proves/does-not-prove boundaries. - Use Case: Before claiming Ray-Ban Display support, run the inspector and iOS preflight runner, then promote evidence one level at a time until the physical script passes on the exact device pair. ## Quick Start Ask the agent to run the target-surface inspector and preflight receipt against your Meta Wearables app workspace and produce an evidence matrix for the capability you want to claim.

Frequently Asked Questions about meta-wearables-device-proof

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

FAQPage Schema
How do I prove a Meta Wearables feature works on physical glasses?▼

Run the target-surface inspector, complete the lowest unmet PRE-* preflight gate, then execute the physical script on the exact device pair covering registration, session, camera/audio, Display, and recovery. Record model, firmware, build, and result per task ID; mock or simulator passes never count as physical proof.

What does the Android target preflight runner check?▼

It inventories the Gradle settings, module build files, DAT Maven coordinates, manifest metadata keys, SDK levels, toolchain presence, and 0.9 migration markers, emitting a redacted JSON receipt. It performs no dependency resolution, compilation, or device testing, so its result is static evidence only.

Can MockDevice or browser simulator results count as on-device evidence?▼

No. MockDevice and browser simulator passes prove only controlled logic and layout behavior. Connected-device results apply only to the named pair, and only the physical script on the exact target glasses proves camera, audio, Display, input, latency, or comfort claims.

Does the iOS preflight runner expose credentials or raw xcodebuild output?▼

No. The runner emits only safe build settings, package-lock facts, and redacted inventory data, explicitly omitting raw xcodebuild output and credential values. Secrets, tokens, serials, and raw media are excluded from all receipts by design.

When should I not promote a build result to release readiness?▼

Never promote while physical, privacy, access, or publishing gates remain open. A signed archive does not prove Meta release-channel delivery or App Store approval, and Gen 2 evidence never generalizes to other generations or models.

Related Skills

Explore More Software Engineering Skills→
facebookfacebook
523

live-debugging-mcp

Diagnose iOS DAT app issues using live MCP debug server events and device state.

Official
Intermediate
ricablericable

expo-deployment

Deploy Expo applications for iOS, Android, and web releases.

Community
Intermediate
even-realitieseven-realities
61

simulator-automation

Automate EvenHub simulator testing via HTTP API for input and output capture.

Official
Intermediate
blacklanternsecurityblacklanternsecurity
253

xss-stored

Guide stored and blind XSS exploitation during authorized penetration tests.

Official
Advanced