Light Remote

View saved version →

---
name: connection-and-onboarding
description: Connect to Light Remote, understand the authorized device topology, and explain the local-first A/B enrollment trust boundary.
---

Use this skill when the user asks to connect to Light Remote, asks what Light Remote can do, or needs help choosing a device.

1. Call `light_remote_connection_helper` first.
2. Explain the currently enrolled topology and effective capabilities without exposing internal identifiers or secrets.
3. 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.
4. Never invent an A code, B code, approval, device, entitlement, or capability.
5. 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.

View saved version →

---
name: fleet-and-device-governance
description: Inspect Main/Fleet topology and safely manage Main, revoke, or remove actions for Light Remote devices.
---

Use this skill when the user asks about Main device, Fleet, multi-device routing, device revocation, or removal.

1. Start with `light_remote_connection_helper` and, when useful, `light_remote_inspect_device`.
2. Treat Main-device selection as an explicit account governance change. Use `light_remote_set_main_device` only for the device the user selected.
3. Never infer or substitute a different device when the requested device is unavailable.
4. Revocation closes a device's remote authority. Removal deletes its enrollment binding and requires fresh local-first enrollment to add it again.
5. Use revoke or remove only after explicit user intent for that named device; do not broaden a single-device request to other devices.
6. After a governance change, re-read topology to confirm the resulting Main/Fleet state.

View saved version →

---
name: policy-and-observability
description: Explain Light Remote policy boundaries, effective permissions, activity, PTY behavior, and update/helper state without bypassing local controls.
---

Use this skill when the user asks why an operation was allowed or denied, wants recent activity, or wants to understand Wall/Fleet/update behavior.

1. Use `light_remote_inspect_device` for routing, effective capabilities, policy, Fleet relationship, and sanitized update/helper status.
2. Use `light_remote_recent_activity` for recent session, job, PTY/process, routing, policy, and update events.
3. Distinguish product capability from effective permission on the selected device.
4. Device-local policy is a final deny boundary. Explain a denial rather than trying another command, another device, sudo, or a policy bypass.
5. Do not request or expose passwords, API keys, MFA/OTP codes, private keys, signing secrets, raw transport credentials, or unnecessary internal identifiers.
6. Treat updater/helper and signing architecture as observable product state, not authority to disable signature checks or obtain signing keys.

View saved version →

---
name: remote-operations
description: Perform governed remote filesystem, search, process, command, and PTY work on one explicit Light Remote device.
---

Use this skill for normal work on an already enrolled Light Remote device.

1. Inspect or list devices and choose the exact target requested by the user.
2. Open or reuse one durable session bound to that device.
3. Prefer structured filesystem and search tools over shell commands when they cover the task.
4. Use managed processes for long-running stdin/stdout work that does not need a real terminal.
5. Use PTY/ConPTY only when interactive terminal semantics are required, including persistent shells, resize, Ctrl-C, or terminal applications.
6. If an operation returns a running job, poll the job and read output instead of repeating the action.
7. Preserve the exact device and session through retries or recovery. Never silently fall back to another device.
8. Respect local policy denials and do not attempt privilege bypasses.