{"id":26376,"plugin_id":"plugin_asdk_app_6aab6c4bd7d88191a4108d8f4c5e4b4e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-04T06:02:49.824Z","digest":"f40551a83055b0e574c5076aa0824f5e00b2f7d574f00f2310b9352b0dd145d0","against":null,"payload":{"description":"Connect to Light Remote, understand the authorized device topology, and explain the local-first A/B enrollment trust boundary.","included_files":[],"name":"connection-and-onboarding","skill_md_contents":"---\nname: connection-and-onboarding\ndescription: Connect to Light Remote, understand the authorized device topology, and explain the local-first A/B enrollment trust boundary.\n---\n\nUse this skill when the user asks to connect to Light Remote, asks what Light Remote can do, or needs help choosing a device.\n\n1. Call `light_remote_connection_helper` first.\n2. Explain the currently enrolled topology and effective capabilities without exposing internal identifiers or secrets.\n3. If the user needs a new device, explain the production enrollment flow accurately: the one-time A code originates from that device's Local Wall; the remote MCP cannot mint it or bypass local approval.\n4. Never invent an A code, B code, approval, device, entitlement, or capability.\n5. Before remote work, keep the target explicit. If the requested target is missing or unavailable, report that condition and do not silently switch to another device.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}