meta-wearables-source-refresh

Refresh Meta Wearables DAT knowledge base with verified source revisions and drift checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve? SDK documentation, repository refs, and device-generation claims drift over time, and acting on stale or inaccessible sources turns guesses into implementation facts. This Skill keeps the Meta Wearables DAT, Web Apps, device, and terms knowledge base current by verifying pinned public Git refs, source-tree inventories, and role manifests before any version-sensitive work. ## Core Features & Use Cases - Public ref drift checking: Runs check_source_revisions.py to compare pinned iOS, Android, and Web App repository commits and tags against live public refs without cloning or credentials. - Source-tree inventory validation: Runs check_source_tree_inventory.py to verify package products, plugin role names and counts, samples, artifacts, SDK levels, references, examples, and templates, with a read-only codeload fallback on API rate limits. - Evidence-bound refresh workflow: Records exact URLs, commits, retrieval dates, migration notes, access gaps, and source-conflict states instead of silently rewriting snapshots. - Use Case: After a Meta DAT 0.9 SDK release, run the refresh to detect drifted refs, compute impacted knowledge-base rows and role packages, update only those entries, and produce a validation receipt. ## Quick Start Ask the agent to refresh the Meta Wearables source knowledge base and run the pinned revision and inventory drift checks before any version-sensitive implementation.

Frequently Asked Questions about meta-wearables-source-refresh

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

FAQPage Schema
How do I check if pinned Meta Wearables SDK refs have drifted?

Run check_source_revisions.py from the skill package. It compares pinned iOS, Android, and Web App repository commits and tags against live public refs using git ls-remote, printing MATCH or DRIFT per check and a summary like CHECKS 23 DRIFT 0.

How to validate Meta DAT repository structure without cloning?

Run check_source_tree_inventory.py, which reads root files, plugin manifests, Package.swift products, role directories, samples, artifacts, and SDK levels through the GitHub Contents API. On unauthenticated rate limits it falls back to a read-only codeload archive.

Does the source refresh require GitHub credentials or cloning?

No. Both checker scripts operate credential-free using git ls-remote, the public Contents API, raw file fetches, and a codeload tarball fallback. They never clone repositories or print credentials.

What happens when the drift check reports DRIFT?

A DRIFT result is a refresh blocker, not permission to silently rewrite the manifest. You compute impacted knowledge-base rows, routes, and role packages, update only those entries, then rerun validators and archive parity.

Can inaccessible or login-gated Wearables docs be treated as facts?

No. The skill records the access state of docs, MCP, and llms.txt endpoints separately and logs gaps when pages require login or cannot be fetched. Unseen content is never summarized or cited as an API contract.