[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM9KZX0V9QQD5D93N7ADA0":3,"skill-same:01M7DM9KZX0V9QQD5D93N7ADA0":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7DM9KZX0V9QQD5D93N7ADA0","cross-host-rig-commands",null,"Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.","mvschwarz\u002Fopenrig-world","mvschwarz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171890339?v=4","01M7DM95A4N5936P8G2FTSPMY7","Mike Schwarz","01M7DM95AX80NY8HZA7XXDYAZR",16,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Fagents\u002Fshared\u002Fskills\u002Fcore\u002Fcross-host-rig-commands\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cross-host-rig-commands\ndescription: Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.\nmetadata:\n  cli_surfaces_referenced:\n    - capture\n    - daemon start\n    - host list\n    - host add\n    - host doctor\n    - ps\n    - send\n    - whoami\n  openrig:\n    stage: factory-approved\n    sibling_skills:\n      - rig-lifecycle\n      - topology-mutation-and-seat-management\n      - seat-scaling-and-specialization\n      - sidecar-operator\n      - rig-bundles-and-shareable-artifacts\n      - specification-system\n      - extension-and-user-workspace\n---\n\n# Cross-host rig commands\n\nUse a registered host address and the entry's declared transport. SSH entries\nrun a remote CLI through a single-hop shell; HTTP entries use the remote daemon.\nThese paths have different prerequisites and command coverage. Check the exact\ncommand's help and the target installation before a consequential operation.\n\n## Choose and inspect the destination\n\n`rig host list` shows registered hosts. `rig host add --help` describes registry\nwrites; `rig host doctor --help` describes reachability checks. Inspect the\nconfigured OpenRig home rather than assuming the default `~\u002F.openrig\u002Fhosts.yaml`.\nRegistry changes affect later routing, so make them within the requested scope.\n\n```yaml\nhosts:\n  - id: test-vm\n    transport: ssh\n    target: test-vm.local\n    user: example-user\n  - id: remote-dev\n    transport: http\n    url: http:\u002F\u002Fremote-dev.example:7433\n    bearer_env: REMOTE_RIG_TOKEN\n```\n\nThe registry requires a hosts array, unique non-empty ids and a supported\ntransport. SSH needs a non-empty target; user and notes are optional. HTTP needs\na URL and accepts at most one of bearer_env or bearer_file. Omitting both is\nvalid for a tokenless target. A configured but unavailable bearer is a permission\nfailure, not anonymous fallback. Host ids also have reserved-name validation;\nuse the actual validator's error rather than inventing an alias that collides.\n\n## Address the intended operation\n\n```bash\nrig send dev-worker@example-rig \"check the assigned result\" --host remote-dev --verify\nrig capture dev-worker@example-rig --host remote-dev\nrig ps --host remote-dev --nodes --json\nrig whoami --host remote-dev\n```\n\nThese coordination commands select SSH or HTTP from the registry entry. They\ndo not silently try another transport when one fails. A host-qualified target\ncan be convenient, but confirm its parsing and any persisted host selection\nwith the particular command. Explicit --host is preferable for consequential\ncross-host work.\n\nQueue destinations use explicit --host or a supported host-qualified destination;\nqueue writes do not follow persisted host selection. The CLI separates the host\nfrom the canonical seat in the routing envelope. Different queue subcommands\nhave different flags: check their help instead of copying a flag from send.\nA local success message alone does not establish remote persistence or pickup.\n\n## Read failures at the layer that failed\n\n| Signal | What to inspect |\n|---|---|\n| registry-load-failed \u002F unknown-host | Registry path, entry and exact destination |\n| ssh-unreachable | SSH connection, target and transport diagnostics |\n| permission-gate | The configured SSH or HTTP credentials and target policy |\n| remote-daemon-unreachable | Target listener and actual running daemon identity |\n| remote-command-not-found | Remote CLI installation and executable lookup |\n| remote-command-failed | The remote operation's own status and error |\n\nThe exact result taxonomy depends on the path. HTTP failures expose the remote\nstatus\u002Ferror; SSH distinguishes the shell transport from the remote command.\nDo not start or replace a remote daemon merely because a diagnostic suggests it;\nfirst establish the target's state and the authority for that lifecycle action.\nA timed-out write may have reached its destination. Reconcile its durable effect\nbefore retrying.\n\n## Verification and attribution\n\nTransport success is not delivery verification or agent consumption. SSH forwards\n--verify and returns the remote CLI result. HTTP preserves the remote transport\nverdict and explicitly reports that the local pane-effect check did not run\ncross-host. Inspect that result and the destination effect required by the task;\nnever replace it with “SSH exited zero” or “HTTP returned successfully.”\n\nCross-host output names the host\u002Ftarget; JSON envelopes carry cross_host metadata.\nThe precise envelope differs by command and transport. Preserve the underlying\nremote result when passing evidence onward.\n\nA target's host suffix selects a destination; a sender's origin identifies where\na reply belongs. Use the rendered reply address and verify its host mapping.\nCurrent send derives the sender from the executing seat context, not a caller's\n--from assertion. It adds origin-host identity at cross-host forwarding; do not\nassume local sends have the same suffix. Unknown identity remains unknown.\n\nThis guide describes the implemented command paths, not proof of a live remote\njourney on your installation. Forks, handovers and other lifecycle compositions\nneed their own supported command and scoped authority; reading remote state\ndoes not authorize them.\n\n## See also\n\n- openrig-user — exact command reference\n- seat-continuity-and-handover — stable seat and occupant outcomes\n","# Cross-host rig commands\n\nUse a registered host address and the entry's declared transport. SSH entries\nrun a remote CLI through a single-hop shell; HTTP entries use the remote daemon.\nThese paths have different prerequisites and command coverage. Check the exact\ncommand's help and the target installation before a consequential operation.\n\n## Choose and inspect the destination\n\n`rig host list` shows registered hosts. `rig host add --help` describes registry\nwrites; `rig host doctor --help` describes reachability checks. Inspect the\nconfigured OpenRig home rather than assuming the default `~\u002F.openrig\u002Fhosts.yaml`.\nRegistry changes affect later routing, so make them within the requested scope.\n\n```yaml\nhosts:\n  - id: test-vm\n    transport: ssh\n    target: test-vm.local\n    user: example-user\n  - id: remote-dev\n    transport: http\n    url: http:\u002F\u002Fremote-dev.example:7433\n    bearer_env: REMOTE_RIG_TOKEN\n```\n\nThe registry requires a hosts array, unique non-empty ids and a supported\ntransport. SSH needs a non-empty target; user and notes are optional. HTTP needs\na URL and accepts at most one of bearer_env or bearer_file. Omitting both is\nvalid for a tokenless target. A configured but unavailable bearer is a permission\nfailure, not anonymous fallback. Host ids also have reserved-name validation;\nuse the actual validator's error rather than inventing an alias that collides.\n\n## Address the intended operation\n\n```bash\nrig send dev-worker@example-rig \"check the assigned result\" --host remote-dev --verify\nrig capture dev-worker@example-rig --host remote-dev\nrig ps --host remote-dev --nodes --json\nrig whoami --host remote-dev\n```\n\nThese coordination commands select SSH or HTTP from the registry entry. They\ndo not silently try another transport when one fails. A host-qualified target\ncan be convenient, but confirm its parsing and any persisted host selection\nwith the particular command. Explicit --host is preferable for consequential\ncross-host work.\n\nQueue destinations use explicit --host or a supported host-qualified destination;\nqueue writes do not follow persisted host selection. The CLI separates the host\nfrom the canonical seat in the routing envelope. Different queue subcommands\nhave different flags: check their help instead of copying a flag from send.\nA local success message alone does not establish remote persistence or pickup.\n\n## Read failures at the layer that failed\n\n| Signal | What to inspect |\n|---|---|\n| registry-load-failed \u002F unknown-host | Registry path, entry and exact destination |\n| ssh-unreachable | SSH connection, target and transport diagnostics |\n| permission-gate | The configured SSH or HTTP credentials and target policy |\n| remote-daemon-unreachable | Target listener and actual running daemon identity |\n| remote-command-not-found | Remote CLI installation and executable lookup |\n| remote-command-failed | The remote operation's own status and error |\n\nThe exact result taxonomy depends on the path. HTTP failures expose the remote\nstatus\u002Ferror; SSH distinguishes the shell transport from the remote command.\nDo not start or replace a remote daemon merely because a diagnostic suggests it;\nfirst establish the target's state and the authority for that lifecycle action.\nA timed-out write may have reached its destination. Reconcile its durable effect\nbefore retrying.\n\n## Verification and attribution\n\nTransport success is not delivery verification or agent consumption. SSH forwards\n--verify and returns the remote CLI result. HTTP preserves the remote transport\nverdict and explicitly reports that the local pane-effect check did not run\ncross-host. Inspect that result and the destination effect required by the task;\nnever replace it with “SSH exited zero” or “HTTP returned successfully.”\n\nCross-host output names the host\u002Ftarget; JSON envelopes carry cross_host metadata.\nThe precise envelope differs by command and transport. Preserve the underlying\nremote result when passing evidence onward.\n\nA target's host suffix selects a destination; a sender's origin identifies where\na reply belongs. Use the rendered reply address and verify its host mapping.\nCurrent send derives the sender from the executing seat context, not a caller's\n--from assertion. It adds origin-host identity at cross-host forwarding; do not\nassume local sends have the same suffix. Unknown identity remains unknown.\n\nThis guide describes the implemented command paths, not proof of a live remote\njourney on your installation. Forks, handovers and other lifecycle compositions\nneed their own supported command and scoped authority; reading remote state\ndoes not authorize them.\n\n## See also\n\n- openrig-user — exact command reference\n- seat-continuity-and-handover — stable seat and occupant outcomes\n",{"name":5,"metadata":24,"description":7},{"openrig":25,"cli_surfaces_referenced":35},{"stage":26,"sibling_skills":27},"factory-approved",[28,29,30,31,32,33,34],"rig-lifecycle","topology-mutation-and-seat-management","seat-scaling-and-specialization","sidecar-operator","rig-bundles-and-shareable-artifacts","specification-system","extension-and-user-workspace",[36,37,38,39,40,41,42,43],"capture","daemon start","host list","host add","host doctor","ps","send","whoami","main","60438a272b68d091eddb01aad6e399af4996d536","agents\u002Fshared\u002Fskills\u002Fcore\u002Fcross-host-rig-commands",4,"https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world","https:\u002F\u002Fgithub.com\u002Fmvschwarz","https:\u002F\u002Fopenrig.dev","Building OpenRig. Running rogue AI civilizations. Debugging their coordination problems.","2026-11-12 13:31:38",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add mvschwarz\u002Fopenrig-world --skill cross-host-rig-commands",{"tool":59,"command":60},"bunx","bunx skills add mvschwarz\u002Fopenrig-world --skill cross-host-rig-commands",{"tool":62,"command":63},"pnpm","pnpm dlx skills add mvschwarz\u002Fopenrig-world --skill cross-host-rig-commands","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Fagents\u002Fshared\u002Fskills\u002Fcore\u002Fcross-host-rig-commands\u002FSKILL.md",true,[],[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DMSEDCRREMBJF57RQB59HC","notes","Use when taking notes.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Ftools\u002Ftest\u002Ffixtures\u002Finstall-verify\u002Fbundle\u002Fagents\u002Fteam\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DMSBZP9WE8MC09JDXFCR2F","software-for-agents","Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsoftware-for-agents\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DMS55VHEAGPXMHZJ7FX94R","session-compaction-and-restore","Use when reasoning about what survives compaction\u002Fcontext-loss\u002Frestart\u002Fseat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet preserves details but loses product intent; runtime resume mistaken for handover or fork; rebuilt seat starts with stale instructions).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsession-compaction-and-restore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DMRYQK0JTV7MMVHFWZ0BW0","seat-continuity-and-handover","Use when replacing a seat's occupant (rebuild\u002Fhandover\u002Fswap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire\u002Fadvise\u002Fshadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fseat-continuity-and-handover\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7DMRP6RRGCJZSH9CE3PC1MY","retiring-and-inheriting-a-seat","Use 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 let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction\u002Fcrash recovery (session-compaction-and-restore \u002F claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fretiring-and-inheriting-a-seat\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7DMRJGN6Z8TZDR7JNHXH6KX","refocusing","Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Frefocusing\u002FSKILL.md",[],[]]