{"id":26377,"plugin_id":"plugin_asdk_app_6aab6c4bd7d88191a4108d8f4c5e4b4e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-04T06:02:49.833Z","digest":"edf9446594ea0aea1eba7cf2f659f205414c357dd53eaa51f02977407a934e2e","against":null,"payload":{"description":"Inspect Main/Fleet topology and safely manage Main, revoke, or remove actions for Light Remote devices.","included_files":[],"name":"fleet-and-device-governance","skill_md_contents":"---\nname: fleet-and-device-governance\ndescription: Inspect Main/Fleet topology and safely manage Main, revoke, or remove actions for Light Remote devices.\n---\n\nUse this skill when the user asks about Main device, Fleet, multi-device routing, device revocation, or removal.\n\n1. Start with `light_remote_connection_helper` and, when useful, `light_remote_inspect_device`.\n2. Treat Main-device selection as an explicit account governance change. Use `light_remote_set_main_device` only for the device the user selected.\n3. Never infer or substitute a different device when the requested device is unavailable.\n4. Revocation closes a device's remote authority. Removal deletes its enrollment binding and requires fresh local-first enrollment to add it again.\n5. Use revoke or remove only after explicit user intent for that named device; do not broaden a single-device request to other devices.\n6. After a governance change, re-read topology to confirm the resulting Main/Fleet state.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}