[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F165D1KY91Q591MEC0XFXV":3,"skill-same:01M7F165D1KY91Q591MEC0XFXV":48},{"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},"01M7F165D1KY91Q591MEC0XFXV","ios-companion-communications",null,"Design, route, implement, or review iOS companion and communication features using WatchConnectivity, CarPlay, App Clips, CallKit, LiveCommunicationKit, PushKit, APNs, and UserNotifications. Use when a feature spans iPhone\u002FWatch, a vehicle screen, an App Clip\u002Ffull app handoff, VoIP\u002Fcalling, default calling\u002Fdialer behavior, or specialized push delivery.","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\u002Fios-ops\u002Fskills\u002Fios-companion-communications\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ios-companion-communications\ndescription: Design, route, implement, or review iOS companion and communication features using WatchConnectivity, CarPlay, App Clips, CallKit, LiveCommunicationKit, PushKit, APNs, and UserNotifications. Use when a feature spans iPhone\u002FWatch, a vehicle screen, an App Clip\u002Ffull app handoff, VoIP\u002Fcalling, default calling\u002Fdialer behavior, or specialized push delivery.\nallowed-tools: Read, Grep, Glob, Edit, Write, Bash\nlast_verified: 2026-08-19\n---\n\n# iOS Companion and Communications\n\nUse this skill to keep paired-device, vehicle, App Clip, push, call, audio, server, and system-UI state separate.\n\n## Read before acting\n\n- Inspect the actual iPhone\u002FWatch\u002FApp Clip\u002FCarPlay targets, bundle identifiers, deployment targets, scene manifests, entitlements, capabilities, associated domains, App Groups, APNs environment, server contract, and audio\u002Fsession adapters.\n- Read the [networking\u002Fcompanion route](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F07-networking-and-collaboration.md), [Watch\u002FCarPlay\u002FApp Clip deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F43-system-framework-deep-dives\u002F04-watch-carplay-and-app-clips.md), [Watch Connectivity state deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F06-watch-connectivity-and-multiplatform.md), and [communication surfaces card](..\u002Fios-knowledge-base\u002Freferences\u002F44-system-services\u002F01-commerce-and-communication-surfaces.md).\n- Refresh the exact official framework pages in the Sources section before relying on current OS\u002Fregion\u002Fdevice availability, an entitlement, push rule, or system-owned UI behavior.\n\n## Routing workflow\n\n1. Identify the user outcome: paired-device state, queued companion event, immediate companion request, vehicle glance\u002Faction, App Clip task, ordinary message, incoming VoIP call, or default calling\u002Fdialer action.\n2. Select the route by semantics: `updateApplicationContext` for latest Watch state, `transferUserInfo` for queued events, `transferFile` for file handoffs, `sendMessage` only for reachable immediate interaction; CarPlay templates for supported vehicle categories; App Clip invocation URLs for focused entry; UserNotifications for ordinary notification; PushKit only for documented VoIP\u002Ffile-provider\u002Fcomplication uses.\n3. Draw the system boundary: `activation\u002Finvocation\u002Ftoken -> validation\u002Faccount\u002Fserver reconciliation -> system-owned surface -> service\u002Faction completion -> fallback`.\n4. Model separate fields for paired, installed, activated, active, reachable, queued, connected, token-registered, call-reported, call-active, stale, failed, and ended. Never reduce them to one `connected` Boolean.\n5. Make every payload versioned, scoped to the correct account\u002Fdevice, bounded, privacy-minimized, and idempotent. Persist revisions\u002Fevent IDs where a duplicate side effect matters.\n6. Define unavailable\u002Ffallback behavior: no Watch, not reachable, inactive watch, CarPlay disconnect, no invocation URL, App Clip replaced by full app, push token rotation, server timeout, call rejection, audio interruption, and no system entitlement.\n7. Test the actual two-device\u002Fsystem surface. A simulator, mock push, local URL, or screenshot does not prove pairing, APNs, vehicle behavior, system call UI, audio, default-role eligibility, or delivery timing.\n\n## Fast path\n\nFreeze one message, call, or notification lifecycle and one user-visible fallback. Trace sender -> transport -> system host -> receiver -> acknowledgment or expiry, then test duplicate, delayed, background, permission, revocation, and disconnect states before adding another companion surface.\n\n## Non-negotiable communication rules\n\n- PushKit is not a general-purpose background wake channel. For VoIP on current SDKs, report the incoming call to CallKit quickly; if the app cannot use CallKit, use UserNotifications instead.\n- A PushKit token\u002Fpayload is not identity, permission, delivery, or an active call. Reconcile with the server and deduplicate call UUIDs.\n- CallKit actions are system commands. Fulfill answer\u002Fend\u002Fhold only after the underlying service\u002Faudio state is ready; fail or report an end reason honestly.\n- LiveCommunicationKit coordinates conversations and possible default roles; it does not provide the VoIP backend or guarantee broad OS\u002Fregion eligibility.\n- CarPlay apps use supported templates and category rules; do not mirror an unrestricted iPhone UI or put dense editing in a driver-facing surface.\n- App Clip URLs are context, not account\u002Fpayment\u002Fpermission proof. Parse and validate them; handle launches without a URL; share the invocation parser with the full app.\n- Watch reachability is only immediate availability. Queued transfers are delayed\u002Fopportunistic; delivery is not server sync.\n- Keep contact, call, location, health, and vehicle metadata out of logs and shared projections unless explicitly needed and retained.\n\n## Deliverable\n\nProduce:\n\n- selected route and rejected alternatives;\n- target, pairing, server, entitlement, APNs, associated-domain, and account matrix;\n- protocol envelope\u002Freducer and state machine;\n- user-facing fallback\u002Foffline\u002Ferror policy;\n- physical\u002Ftwo-device\u002Fsystem-surface evidence plan;\n- source links and unproven claims.\n\nDuring implementation, preserve target boundaries and do not add server accounts, VoIP pushes, telephony\u002Fdefault-role entitlements, tracking, recording, or external communications without explicit need and authorization.\n\n## Related recipes\n\n- [Watch, CarPlay, App Clip, and communication recipes](..\u002Fios-knowledge-base\u002Freferences\u002F70-code-recipes\u002F20-watch-carplay-appclips-and-communications-recipes.md)\n- [Watch\u002FCarPlay\u002FApp Clip deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F43-system-framework-deep-dives\u002F04-watch-carplay-and-app-clips.md)\n- [Watch Connectivity and multiplatform state](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F06-watch-connectivity-and-multiplatform.md)\n- [System-surface checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F05-system-surface-checklist.md)\n- [Build\u002Fdevice\u002Frelease checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F01-build-device-and-release-checklist.md)\n\n## Sources\n\n- [Watch Connectivity](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity)\n- [WCSession](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity\u002Fwcsession)\n- [WCSessionDelegate](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity\u002Fwcsessiondelegate)\n- [Transferring data with Watch Connectivity](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity\u002Ftransferring-data-with-watch-connectivity)\n- [CarPlay](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay)\n- [CPTemplateApplicationScene](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay\u002Fcptemplateapplicationscene)\n- [CPInterfaceController](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay\u002Fcpinterfacecontroller)\n- [Displaying content in CarPlay](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay\u002Fdisplaying-content-in-carplay)\n- [App Clips](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fappclip)\n- [Responding to invocations](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fappclip\u002Fresponding-to-invocations)\n- [CallKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcallkit)\n- [CXProvider](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcallkit\u002Fcxprovider)\n- [Making and receiving VoIP calls](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcallkit\u002Fmaking-and-receiving-voip-calls)\n- [LiveCommunicationKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Flivecommunicationkit)\n- [PushKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fpushkit)\n- [PKPushRegistry](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fpushkit\u002Fpkpushregistry)\n- [Responding to VoIP Notifications from PushKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fpushkit\u002Fresponding-to-voip-notifications-from-pushkit)\n- [UserNotifications](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fusernotifications)\n","# iOS Companion and Communications\n\nUse this skill to keep paired-device, vehicle, App Clip, push, call, audio, server, and system-UI state separate.\n\n## Read before acting\n\n- Inspect the actual iPhone\u002FWatch\u002FApp Clip\u002FCarPlay targets, bundle identifiers, deployment targets, scene manifests, entitlements, capabilities, associated domains, App Groups, APNs environment, server contract, and audio\u002Fsession adapters.\n- Read the [networking\u002Fcompanion route](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F07-networking-and-collaboration.md), [Watch\u002FCarPlay\u002FApp Clip deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F43-system-framework-deep-dives\u002F04-watch-carplay-and-app-clips.md), [Watch Connectivity state deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F06-watch-connectivity-and-multiplatform.md), and [communication surfaces card](..\u002Fios-knowledge-base\u002Freferences\u002F44-system-services\u002F01-commerce-and-communication-surfaces.md).\n- Refresh the exact official framework pages in the Sources section before relying on current OS\u002Fregion\u002Fdevice availability, an entitlement, push rule, or system-owned UI behavior.\n\n## Routing workflow\n\n1. Identify the user outcome: paired-device state, queued companion event, immediate companion request, vehicle glance\u002Faction, App Clip task, ordinary message, incoming VoIP call, or default calling\u002Fdialer action.\n2. Select the route by semantics: `updateApplicationContext` for latest Watch state, `transferUserInfo` for queued events, `transferFile` for file handoffs, `sendMessage` only for reachable immediate interaction; CarPlay templates for supported vehicle categories; App Clip invocation URLs for focused entry; UserNotifications for ordinary notification; PushKit only for documented VoIP\u002Ffile-provider\u002Fcomplication uses.\n3. Draw the system boundary: `activation\u002Finvocation\u002Ftoken -> validation\u002Faccount\u002Fserver reconciliation -> system-owned surface -> service\u002Faction completion -> fallback`.\n4. Model separate fields for paired, installed, activated, active, reachable, queued, connected, token-registered, call-reported, call-active, stale, failed, and ended. Never reduce them to one `connected` Boolean.\n5. Make every payload versioned, scoped to the correct account\u002Fdevice, bounded, privacy-minimized, and idempotent. Persist revisions\u002Fevent IDs where a duplicate side effect matters.\n6. Define unavailable\u002Ffallback behavior: no Watch, not reachable, inactive watch, CarPlay disconnect, no invocation URL, App Clip replaced by full app, push token rotation, server timeout, call rejection, audio interruption, and no system entitlement.\n7. Test the actual two-device\u002Fsystem surface. A simulator, mock push, local URL, or screenshot does not prove pairing, APNs, vehicle behavior, system call UI, audio, default-role eligibility, or delivery timing.\n\n## Fast path\n\nFreeze one message, call, or notification lifecycle and one user-visible fallback. Trace sender -> transport -> system host -> receiver -> acknowledgment or expiry, then test duplicate, delayed, background, permission, revocation, and disconnect states before adding another companion surface.\n\n## Non-negotiable communication rules\n\n- PushKit is not a general-purpose background wake channel. For VoIP on current SDKs, report the incoming call to CallKit quickly; if the app cannot use CallKit, use UserNotifications instead.\n- A PushKit token\u002Fpayload is not identity, permission, delivery, or an active call. Reconcile with the server and deduplicate call UUIDs.\n- CallKit actions are system commands. Fulfill answer\u002Fend\u002Fhold only after the underlying service\u002Faudio state is ready; fail or report an end reason honestly.\n- LiveCommunicationKit coordinates conversations and possible default roles; it does not provide the VoIP backend or guarantee broad OS\u002Fregion eligibility.\n- CarPlay apps use supported templates and category rules; do not mirror an unrestricted iPhone UI or put dense editing in a driver-facing surface.\n- App Clip URLs are context, not account\u002Fpayment\u002Fpermission proof. Parse and validate them; handle launches without a URL; share the invocation parser with the full app.\n- Watch reachability is only immediate availability. Queued transfers are delayed\u002Fopportunistic; delivery is not server sync.\n- Keep contact, call, location, health, and vehicle metadata out of logs and shared projections unless explicitly needed and retained.\n\n## Deliverable\n\nProduce:\n\n- selected route and rejected alternatives;\n- target, pairing, server, entitlement, APNs, associated-domain, and account matrix;\n- protocol envelope\u002Freducer and state machine;\n- user-facing fallback\u002Foffline\u002Ferror policy;\n- physical\u002Ftwo-device\u002Fsystem-surface evidence plan;\n- source links and unproven claims.\n\nDuring implementation, preserve target boundaries and do not add server accounts, VoIP pushes, telephony\u002Fdefault-role entitlements, tracking, recording, or external communications without explicit need and authorization.\n\n## Related recipes\n\n- [Watch, CarPlay, App Clip, and communication recipes](..\u002Fios-knowledge-base\u002Freferences\u002F70-code-recipes\u002F20-watch-carplay-appclips-and-communications-recipes.md)\n- [Watch\u002FCarPlay\u002FApp Clip deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F43-system-framework-deep-dives\u002F04-watch-carplay-and-app-clips.md)\n- [Watch Connectivity and multiplatform state](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F06-watch-connectivity-and-multiplatform.md)\n- [System-surface checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F05-system-surface-checklist.md)\n- [Build\u002Fdevice\u002Frelease checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F01-build-device-and-release-checklist.md)\n\n## Sources\n\n- [Watch Connectivity](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity)\n- [WCSession](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity\u002Fwcsession)\n- [WCSessionDelegate](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity\u002Fwcsessiondelegate)\n- [Transferring data with Watch Connectivity](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fwatchconnectivity\u002Ftransferring-data-with-watch-connectivity)\n- [CarPlay](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay)\n- [CPTemplateApplicationScene](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay\u002Fcptemplateapplicationscene)\n- [CPInterfaceController](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay\u002Fcpinterfacecontroller)\n- [Displaying content in CarPlay](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcarplay\u002Fdisplaying-content-in-carplay)\n- [App Clips](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fappclip)\n- [Responding to invocations](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fappclip\u002Fresponding-to-invocations)\n- [CallKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcallkit)\n- [CXProvider](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcallkit\u002Fcxprovider)\n- [Making and receiving VoIP calls](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fcallkit\u002Fmaking-and-receiving-voip-calls)\n- [LiveCommunicationKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Flivecommunicationkit)\n- [PushKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fpushkit)\n- [PKPushRegistry](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fpushkit\u002Fpkpushregistry)\n- [Responding to VoIP Notifications from PushKit](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fpushkit\u002Fresponding-to-voip-notifications-from-pushkit)\n- [UserNotifications](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Fusernotifications)\n",{"name":5,"description":7,"allowed-tools":24,"last_verified":25},"Read, Grep, Glob, Edit, Write, Bash",1787097600000,"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fios-ops\u002Fskills\u002Fios-companion-communications","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 ios-companion-communications",{"tool":40,"command":41},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill ios-companion-communications",{"tool":43,"command":44},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill ios-companion-communications","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-companion-communications\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"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":52,"categories":53,"keywords":54,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]