← Light RemoteCONTENT HISTORY

Update to Light Remote

Snapshot Oct 4, 2026 · 06:02 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "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"
}

SHA-256 of public snapshot: edf9446594ea0aea1eba7cf2f659f205414c357dd53eaa51f02977407a934e2e