cross-host-rig-commands

by mvschwarz7.5k

Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a cursor -y

Download skill packages/daemon/specs/agents/shared/skills/core/cross-host-rig-commands/SKILL.md on GitHub

Related skills

View all

R
retiring-and-inheriting-a-seatUse when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than
S
software-for-agents>-
S
session-compaction-and-restoreUse when reasoning about what survives compaction/context-loss/restart/seat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental

Questions

How do I install cross-host-rig-commands?: Download packages/daemon/specs/agents/shared/skills/core/cross-host-rig-commands/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does cross-host-rig-commands live?: The publisher keeps it at https://github.com/mvschwarz/openrig.
Which agents can use cross-host-rig-commands?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: cross-host-rig-commands description: Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result. metadata: cli_surfaces_referenced: - capture - daemon start - host list - host add - host doctor - ps - send - whoami openrig: stage: factory-approved sibling_skills: - rig-lifecycle - topology-mutation-and-seat-management - seat-scaling-and-specialization - sidecar-operator - rig-bundles-and-shareable-artifacts - specification-system - extension-and-user-workspace

Cross-host rig commands

Use a registered host address and the entry's declared transport. SSH entries run a remote CLI through a single-hop shell; HTTP entries use the remote daemon. These paths have different prerequisites and command coverage. Check the exact command's help and the target installation before a consequential operation.

Signal	What to inspect
registry-load-failed / unknown-host	Registry path, entry and exact destination
ssh-unreachable	SSH connection, target and transport diagnostics
permission-gate	The configured SSH or HTTP credentials and target policy
remote-daemon-unreachable	Target listener and actual running daemon identity
remote-outcome-unknown	The request may have arrived (timeout, dropped connection, unreadable reply): check its effect, for a send the target pane, before any retry
remote-command-not-found	Remote CLI installation and executable lookup
remote-command-failed	The remote operation's own status and error

cross-host-rig-commands

Install

Related skills

Questions

Cross-host rig commands

Choose and inspect the destination

Address the intended operation

Read failures at the layer that failed

Verification and attribution

See also