[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1FSNMB8VVB91N2NNP84V3":3,"skill-same:01M7F1FSNMB8VVB91N2NNP84V3":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F1FSNMB8VVB91N2NNP84V3","meta-wearables-diagnostics",null,"Diagnose and recover Meta Wearables DAT iOS\u002FAndroid, native Display, and Display Web App failures, and resolve device and version compatibility — first failing state across registration, permissions, link, session, camera\u002Faudio\u002FDisplay, transport, firmware, and companion, with a redacted diagnostic bundle and a validated compatibility packet. Use when a DAT app cannot reach the glasses, registration or a session fails, an update-required or device-unavailable error appears, firmware or Meta AI versions drift, or someone asks whether a named product such as Gen 2 or Gen 3 supports a capability.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: meta-wearables-diagnostics\ndescription: Diagnose and recover Meta Wearables DAT iOS\u002FAndroid, native Display, and Display Web App failures, and resolve device and version compatibility — first failing state across registration, permissions, link, session, camera\u002Faudio\u002FDisplay, transport, firmware, and companion, with a redacted diagnostic bundle and a validated compatibility packet. Use when a DAT app cannot reach the glasses, registration or a session fails, an update-required or device-unavailable error appears, firmware or Meta AI versions drift, or someone asks whether a named product such as Gen 2 or Gen 3 supports a capability.\nallowed-tools: Read, Grep, Glob, Bash(uv run *)\nlast_verified: 2026-08-22\n---\n\n# Meta Wearables diagnostics\n\nFind the first failing state, apply the least invasive documented recovery, and\ndecide compatibility from an observed version tuple, never from a product label.\nDiagnosis is observation: it is not permission to change the Meta AI app, the\nglasses, the account, registration, or a release channel.\n\nApply the [shared rules](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002Fshared-rules.md) — evidence ladder, device labels, secrets, claims.\n\n## Read before acting\n\n- First failure: the [diagnostic contract](references\u002Fdiagnostic-contract.md) and the\n  [debugging and observability route](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F23-debugging-observability-and-diagnostic-evidence.md).\n- Recovery and readiness: the [recovery contract](references\u002Frecovery-contract.md) and the\n  [operational readiness route](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F18-operational-readiness-and-recovery.md).\n- Compatibility: the [compatibility contract](references\u002Fcompatibility-contract.md), the\n  [version-dependency route](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F26-version-dependency-and-device-compatibility-evidence.md), and the\n  [device-generation matrix](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F16-device-generation-and-runtime-support-matrix.md).\n- Transport, audio, or thermal faults: [transport and runtime reliability](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F22-transport-audio-and-runtime-reliability.md).\n- Refresh the [DAT iOS changelog](https:\u002F\u002Fgithub.com\u002Ffacebook\u002Fmeta-wearables-dat-ios\u002Fblob\u002Fmain\u002FCHANGELOG.md),\n  [DAT Android changelog](https:\u002F\u002Fgithub.com\u002Ffacebook\u002Fmeta-wearables-dat-android\u002Fblob\u002Fmain\u002FCHANGELOG.md),\n  [version dependencies](https:\u002F\u002Fwearables.developer.meta.com\u002Fdocs\u002Fdevelop\u002Fdat\u002Fversion-dependencies\u002F), and\n  [known issues](https:\u002F\u002Fwearables.developer.meta.com\u002Fdocs\u002Fknownissues) before a version-sensitive call.\n  A login-gated table stays `access-gated` until the account view is observed.\n\n## Workflow\n\n1. **Freeze the tuple.** Platform, app build, SDK package or artifact and tag,\n   phone OS, Meta AI version, glasses firmware, on-glasses DAT app version,\n   product label, runtime device type, account mode (Developer Mode or release\n   channel), and the one operation being attempted. Mark gaps `to-verify`.\n2. **Collect the baseline.** If a DAT live-debugging MCP server is connected,\n   discover its tools and use them read-only. If none is connected, fall back to\n   platform logs (the Xcode console or Console.app filtered to the app's `os_log`\n   subsystem; `adb logcat --pid=$(adb shell pidof \u003Capplication.id>)`), the app's\n   own logged DAT registration, device, link, session, and typed-error\n   transitions, a MockDevice reproduction of the same operation, and a\n   hand-built redacted diagnostic bundle. The\n   [diagnostic contract](references\u002Fdiagnostic-contract.md#observation-sources) lists the steps.\n3. **Walk the path in order:** initialization and configuration -> callback ->\n   registration -> permission -> device eligibility and compatibility -> link ->\n   session -> camera\u002Faudio\u002FDisplay -> transport -> thermal\u002Fpower. The first\n   transition that fails owns the diagnosis; record later failures as symptoms.\n   Use the platform's own typed errors; never translate iOS and Android symbols.\n4. **Reproduce once, narrowly.** One operation, one run ID; stop at the earliest\n   actionable boundary.\n5. **Recover with the least invasive documented step,** then re-run the same\n   operation under a new run ID. Never auto-retry through thermal emergency,\n   critical battery, power shutdown, doff\u002Fhinge closure, or an unknown protocol\n   error. A firmware update, DAT-app update, or re-pair counts as successful only\n   when the post-action state is reported and the original operation completes.\n6. **Resolve compatibility per capability.** Compare each tuple member with the\n   official version-dependency surface and label it `source`, `observed`,\n   `access-gated`, `conflict`, or `unknown`. Exercise each requested capability\n   on its own, including a negative path, and give a fallback for every\n   unresolved one.\n7. **Validate the packet.** Fill the\n   [compatibility packet template](references\u002Fcompatibility-evidence-packet.yaml)\n   and run the validator below before handing off.\n\n## Running the validator\n\n`$SKILL` below is this skill's directory — the folder holding this SKILL.md.\nFind it by name in your tool's skills folder (some tools prefix it, e.g.\n`meta-wearables-ops__meta-wearables-diagnostics`).\n\n```bash\nuv run $SKILL\u002Fscripts\u002Fvalidate_compatibility_packet.py \u003Cpacket.yaml>\n```\n\nA `completed` packet needs connected-tuple, physical-capability, and release\nevidence rows. A Gen 3 packet cannot close without `COMP-GEN3-01` physical and\nrelease evidence.\n\n## Hard boundaries\n\n- Do not register, unregister, change permissions, re-pair, update firmware, or\n  switch a channel during diagnosis unless the user authorizes that operation.\n- Do not diagnose from a generic \"not connected\" message when the first failing\n  state can be observed.\n- A debug-server or log result is app-visible evidence through the DAT\n  boundary, not introspection of the Meta AI companion.\n- A GitHub issue or forum report is a troubleshooting signal, never a\n  compatibility guarantee. Label it separately.\n- Developer Mode success is not release-channel evidence. Re-test with the\n  signed build, tester account, and exact firmware before calling a route ready.\n\n## Required output\n\n1. Frozen tuple with each field labeled `source`, `observed`, `access-gated`,\n   or `to-verify`, plus the evidence level reached.\n2. Baseline source used (MCP server, or the named fallback steps) and the\n   ordered event trace with the exact first failing state.\n3. Likely owner: app, SDK\u002Fconfig, Meta AI boundary, device\u002Ffirmware, transport,\n   audio, thermal\u002Fpower, or release channel.\n4. Recovery attempted, post-action state, and whether the original operation\n   then completed.\n5. Capability-by-capability status (`current`, `to-verify`, `device-gated`,\n   `source-conflict`, `unsupported`) with a fallback for each gap, and explicit\n   Gen 2 \u002F Gen 3 treatment.\n6. Evidence rows (`DBG-*`, `OPS-*`, `COMP-*`) with redaction status and the\n   validator receipt.\n7. Verdict — `ready`, `ready-for-device`, `blocked`, `source-conflict`, or\n   `to-verify` — with the proof still missing and the next refresh trigger.\n\n## Related skills\n\n- [Route planner](..\u002Fmeta-wearables-route-planner\u002FSKILL.md) — pick the surface first.\n- [DAT integration](..\u002Fmeta-wearables-dat-integration\u002FSKILL.md) — fix an app or SDK\u002Fconfig defect.\n- [Device capabilities](..\u002Fmeta-wearables-device-capabilities\u002FSKILL.md) — camera, audio, Display, input, transport.\n- [Device proof](..\u002Fmeta-wearables-device-proof\u002FSKILL.md) — physical and signed evidence.\n- [Trust and release](..\u002Fmeta-wearables-trust-and-release\u002FSKILL.md) — identity, callback, attestation, channel failures.\n\n","# Meta Wearables diagnostics\n\nFind the first failing state, apply the least invasive documented recovery, and\ndecide compatibility from an observed version tuple, never from a product label.\nDiagnosis is observation: it is not permission to change the Meta AI app, the\nglasses, the account, registration, or a release channel.\n\nApply the [shared rules](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002Fshared-rules.md) — evidence ladder, device labels, secrets, claims.\n\n## Read before acting\n\n- First failure: the [diagnostic contract](references\u002Fdiagnostic-contract.md) and the\n  [debugging and observability route](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F23-debugging-observability-and-diagnostic-evidence.md).\n- Recovery and readiness: the [recovery contract](references\u002Frecovery-contract.md) and the\n  [operational readiness route](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F18-operational-readiness-and-recovery.md).\n- Compatibility: the [compatibility contract](references\u002Fcompatibility-contract.md), the\n  [version-dependency route](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F26-version-dependency-and-device-compatibility-evidence.md), and the\n  [device-generation matrix](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F16-device-generation-and-runtime-support-matrix.md).\n- Transport, audio, or thermal faults: [transport and runtime reliability](..\u002Fmeta-wearables-knowledge-base\u002Freferences\u002F70-meta-wearables\u002F22-transport-audio-and-runtime-reliability.md).\n- Refresh the [DAT iOS changelog](https:\u002F\u002Fgithub.com\u002Ffacebook\u002Fmeta-wearables-dat-ios\u002Fblob\u002Fmain\u002FCHANGELOG.md),\n  [DAT Android changelog](https:\u002F\u002Fgithub.com\u002Ffacebook\u002Fmeta-wearables-dat-android\u002Fblob\u002Fmain\u002FCHANGELOG.md),\n  [version dependencies](https:\u002F\u002Fwearables.developer.meta.com\u002Fdocs\u002Fdevelop\u002Fdat\u002Fversion-dependencies\u002F), and\n  [known issues](https:\u002F\u002Fwearables.developer.meta.com\u002Fdocs\u002Fknownissues) before a version-sensitive call.\n  A login-gated table stays `access-gated` until the account view is observed.\n\n## Workflow\n\n1. **Freeze the tuple.** Platform, app build, SDK package or artifact and tag,\n   phone OS, Meta AI version, glasses firmware, on-glasses DAT app version,\n   product label, runtime device type, account mode (Developer Mode or release\n   channel), and the one operation being attempted. Mark gaps `to-verify`.\n2. **Collect the baseline.** If a DAT live-debugging MCP server is connected,\n   discover its tools and use them read-only. If none is connected, fall back to\n   platform logs (the Xcode console or Console.app filtered to the app's `os_log`\n   subsystem; `adb logcat --pid=$(adb shell pidof \u003Capplication.id>)`), the app's\n   own logged DAT registration, device, link, session, and typed-error\n   transitions, a MockDevice reproduction of the same operation, and a\n   hand-built redacted diagnostic bundle. The\n   [diagnostic contract](references\u002Fdiagnostic-contract.md#observation-sources) lists the steps.\n3. **Walk the path in order:** initialization and configuration -> callback ->\n   registration -> permission -> device eligibility and compatibility -> link ->\n   session -> camera\u002Faudio\u002FDisplay -> transport -> thermal\u002Fpower. The first\n   transition that fails owns the diagnosis; record later failures as symptoms.\n   Use the platform's own typed errors; never translate iOS and Android symbols.\n4. **Reproduce once, narrowly.** One operation, one run ID; stop at the earliest\n   actionable boundary.\n5. **Recover with the least invasive documented step,** then re-run the same\n   operation under a new run ID. Never auto-retry through thermal emergency,\n   critical battery, power shutdown, doff\u002Fhinge closure, or an unknown protocol\n   error. A firmware update, DAT-app update, or re-pair counts as successful only\n   when the post-action state is reported and the original operation completes.\n6. **Resolve compatibility per capability.** Compare each tuple member with the\n   official version-dependency surface and label it `source`, `observed`,\n   `access-gated`, `conflict`, or `unknown`. Exercise each requested capability\n   on its own, including a negative path, and give a fallback for every\n   unresolved one.\n7. **Validate the packet.** Fill the\n   [compatibility packet template](references\u002Fcompatibility-evidence-packet.yaml)\n   and run the validator below before handing off.\n\n## Running the validator\n\n`$SKILL` below is this skill's directory — the folder holding this SKILL.md.\nFind it by name in your tool's skills folder (some tools prefix it, e.g.\n`meta-wearables-ops__meta-wearables-diagnostics`).\n\n```bash\nuv run $SKILL\u002Fscripts\u002Fvalidate_compatibility_packet.py \u003Cpacket.yaml>\n```\n\nA `completed` packet needs connected-tuple, physical-capability, and release\nevidence rows. A Gen 3 packet cannot close without `COMP-GEN3-01` physical and\nrelease evidence.\n\n## Hard boundaries\n\n- Do not register, unregister, change permissions, re-pair, update firmware, or\n  switch a channel during diagnosis unless the user authorizes that operation.\n- Do not diagnose from a generic \"not connected\" message when the first failing\n  state can be observed.\n- A debug-server or log result is app-visible evidence through the DAT\n  boundary, not introspection of the Meta AI companion.\n- A GitHub issue or forum report is a troubleshooting signal, never a\n  compatibility guarantee. Label it separately.\n- Developer Mode success is not release-channel evidence. Re-test with the\n  signed build, tester account, and exact firmware before calling a route ready.\n\n## Required output\n\n1. Frozen tuple with each field labeled `source`, `observed`, `access-gated`,\n   or `to-verify`, plus the evidence level reached.\n2. Baseline source used (MCP server, or the named fallback steps) and the\n   ordered event trace with the exact first failing state.\n3. Likely owner: app, SDK\u002Fconfig, Meta AI boundary, device\u002Ffirmware, transport,\n   audio, thermal\u002Fpower, or release channel.\n4. Recovery attempted, post-action state, and whether the original operation\n   then completed.\n5. Capability-by-capability status (`current`, `to-verify`, `device-gated`,\n   `source-conflict`, `unsupported`) with a fallback for each gap, and explicit\n   Gen 2 \u002F Gen 3 treatment.\n6. Evidence rows (`DBG-*`, `OPS-*`, `COMP-*`) with redaction status and the\n   validator receipt.\n7. Verdict — `ready`, `ready-for-device`, `blocked`, `source-conflict`, or\n   `to-verify` — with the proof still missing and the next refresh trigger.\n\n## Related skills\n\n- [Route planner](..\u002Fmeta-wearables-route-planner\u002FSKILL.md) — pick the surface first.\n- [DAT integration](..\u002Fmeta-wearables-dat-integration\u002FSKILL.md) — fix an app or SDK\u002Fconfig defect.\n- [Device capabilities](..\u002Fmeta-wearables-device-capabilities\u002FSKILL.md) — camera, audio, Display, input, transport.\n- [Device proof](..\u002Fmeta-wearables-device-proof\u002FSKILL.md) — physical and signed evidence.\n- [Trust and release](..\u002Fmeta-wearables-trust-and-release\u002FSKILL.md) — identity, callback, attestation, channel failures.\n\n",{"name":5,"description":7,"allowed-tools":24,"last_verified":25},"Read, Grep, Glob, Bash(uv run *)",1787356800000,"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill meta-wearables-diagnostics",{"tool":40,"command":41},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill meta-wearables-diagnostics",{"tool":43,"command":44},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill meta-wearables-diagnostics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcompatibility-contract.md","REFERENCE","参考文档",4145,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002Freferences\u002Fcompatibility-contract.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcompatibility-evidence-packet.yaml",4211,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002Freferences\u002Fcompatibility-evidence-packet.yaml",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdiagnostic-contract.md",6093,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002Freferences\u002Fdiagnostic-contract.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Frecovery-contract.md",5326,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002Freferences\u002Frecovery-contract.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fvalidate_compatibility_packet.py","SCRIPT","脚本",14474,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmeta-wearables-ops\u002Fskills\u002Fmeta-wearables-diagnostics\u002Fscripts\u002Fvalidate_compatibility_packet.py",[73,79,86,93,100,107],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]