MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
A skill your agent uses when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.
Install Cross Host Rig Commands
$ npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvschwarz/openrig cross-host-rig-commands --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/core/cross-host-rig-commands .claude/skills/cross-host-rig-commands && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cross-host-rig-commands" agent skill from https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commands into .claude/skills/cross-host-rig-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-host-rig-commands", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commandsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvschwarz/openrig cross-host-rig-commands --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/_canonical/core/cross-host-rig-commands .agents/skills/cross-host-rig-commands && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cross-host-rig-commands" agent skill from https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commands into .agents/skills/cross-host-rig-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-host-rig-commands", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvschwarz/openrig cross-host-rig-commands --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/_canonical/core/cross-host-rig-commands .cursor/skills/cross-host-rig-commands && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cross-host-rig-commands" agent skill from https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commands into .cursor/skills/cross-host-rig-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-host-rig-commands", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvschwarz/openrig.git --path skills/_canonical/core/cross-host-rig-commands--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvschwarz/openrig cross-host-rig-commands --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/_canonical/core/cross-host-rig-commands .gemini/skills/cross-host-rig-commands && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cross-host-rig-commands" agent skill from https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commands into .gemini/skills/cross-host-rig-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-host-rig-commands", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvschwarz/openrig cross-host-rig-commandsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/_canonical/core/cross-host-rig-commands .github/skills/cross-host-rig-commands && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cross-host-rig-commands" agent skill from https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commands into .github/skills/cross-host-rig-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-host-rig-commands", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvschwarz/openrig cross-host-rig-commands --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/_canonical/core/cross-host-rig-commands .opencode/skills/cross-host-rig-commands && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cross-host-rig-commands" agent skill from https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/core/cross-host-rig-commands into .opencode/skills/cross-host-rig-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-host-rig-commands", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cross-host-rig-commands- GitHub stars
- 6.6k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 626 words
- Files
- 1
- Skills in repo
- 49
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.
- Addressing a registered remote OpenRig host
- SKILL.md covers Choose and inspect the…, Address the intended operation, Read failures at the layer… and Verification and attribution, plus 1 more section
- Needs REMOTE_RIG_TOKEN
- Choosing its transport
What it does
Cross Host Rig Commands is an agent skill from mvschwarz/openrig. Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.
When your agent uses it
- Addressing a registered remote OpenRig host
- Choosing its transport
- Interpreting a cross-host result
Example prompts
- “/cross-host-rig-commands”
Requirements
- A credential in REMOTE_RIG_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit 4b48ca2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
REMOTE_RIG_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cross Host Rig Commands loads about 1.4k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 626 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mvschwarz/openrig at commit 4b48ca2, republished under its Apache-2.0 licence (© mvschwarz). 626 words, ~1,384 tokens.
Download SKILL.mdSave it as
.claude/skills/cross-host-rig-commands/SKILL.md (or your agent's skills folder).- 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
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.
Choose and inspect the destination
rig host list shows registered hosts. rig host add --help describes registry
writes; rig host doctor --help describes reachability checks. Inspect the
configured OpenRig home rather than assuming the default ~/.openrig/hosts.yaml.
Registry changes affect later routing, so make them within the requested scope.
hosts:
- id: test-vm
transport: ssh
target: test-vm.local
user: example-user
- id: remote-dev
transport: http
url: http://remote-dev.example:7433
bearer_env: REMOTE_RIG_TOKENThe registry requires a hosts array, unique non-empty ids and a supported transport. SSH needs a non-empty target; user and notes are optional. HTTP needs a URL and accepts at most one of bearer_env or bearer_file. Omitting both is valid for a tokenless target. A configured but unavailable bearer is a permission failure, not anonymous fallback. Host ids also have reserved-name validation; use the actual validator's error rather than inventing an alias that collides.
Address the intended operation
rig send dev-worker@example-rig "check the assigned result" --host remote-dev --verify
rig capture dev-worker@example-rig --host remote-dev
rig ps --host remote-dev --nodes --json
rig whoami --host remote-devThese coordination commands select SSH or HTTP from the registry entry. They do not silently try another transport when one fails. A host-qualified target can be convenient, but confirm its parsing and any persisted host selection with the particular command. Explicit --host is preferable for consequential cross-host work.
Queue destinations use explicit --host or a supported host-qualified destination; queue writes do not follow persisted host selection. The CLI separates the host from the canonical seat in the routing envelope. Different queue subcommands have different flags: check their help instead of copying a flag from send. A local success message alone does not establish remote persistence or pickup.
Read failures at the layer that failed
| 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 |
The exact result taxonomy depends on the path. HTTP failures expose the remote status/error; SSH distinguishes the shell transport from the remote command. Do not start or replace a remote daemon merely because a diagnostic suggests it; first establish the target's state and the authority for that lifecycle action. A timed-out write may have reached its destination. Reconcile its durable effect before retrying.
Show full SKILL.md (198 more words)Show less
Verification and attribution
Transport success is not delivery verification or agent consumption. SSH forwards --verify and returns the remote CLI result. HTTP preserves the remote transport verdict and explicitly reports that the local pane-effect check did not run cross-host. Inspect that result and the destination effect required by the task; never replace it with “SSH exited zero” or “HTTP returned successfully.”
Cross-host output names the host/target; JSON envelopes carry cross_host metadata. The precise envelope differs by command and transport. Preserve the underlying remote result when passing evidence onward.
A target's host suffix selects a destination; a sender's origin identifies where a reply belongs. Use the rendered reply address and verify its host mapping. Current send derives the sender from the executing seat context, not a caller's --from assertion. It adds origin-host identity at cross-host forwarding; do not assume local sends have the same suffix. Unknown identity remains unknown.
This guide describes the implemented command paths, not proof of a live remote journey on your installation. Forks, handovers and other lifecycle compositions need their own supported command and scoped authority; reading remote state does not authorize them.
See also
- openrig-user — exact command reference
- seat-continuity-and-handover — stable seat and occupant outcomes
© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/_canonical/core/cross-host-rig-commands of mvschwarz/openrig.
Open the folder on GitHubat commit 4b48ca2
Compare with similar skills
Cross Host Rig Commands next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cross Host Rig Commands this skillmvschwarz/openrig | 6.6k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from mvschwarz/openrig
All 49 skills in this repoOpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
Agent Refocusing
mvschwarz/openrig
Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.
OpenRig Software Factory
mvschwarz/openrig
Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.
Seat Continuity and Handover
mvschwarz/openrig
Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.
Addressable Markdown Loader
mvschwarz/openrig
Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.
Agent Starters
mvschwarz/openrig
Covers authoring, inspecting, refreshing, promoting and deprecating named Agent Starters, the reusable starting points for agent seats in a rig.
Related
Categories
Questions about Cross Host Rig Commands
What does Cross Host Rig Commands do?
A skill your agent uses when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result. Cross Host Rig Commands is an agent skill from mvschwarz/openrig. Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.
When should I use Cross Host Rig Commands?
Cross Host Rig Commands fits situations like: addressing a registered remote OpenRig host; choosing its transport; interpreting a cross-host result.
How do I install Cross Host Rig Commands in Claude Code?
Run `npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a claude-code`. Or copy the skill folder (skills/_canonical/core/cross-host-rig-commands in mvschwarz/openrig) into .claude/skills/cross-host-rig-commands in your project. Claude Code loads it when a task matches its description.
How do I install Cross Host Rig Commands in Codex?
Run `npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a codex`. Or copy the skill folder (skills/_canonical/core/cross-host-rig-commands in mvschwarz/openrig) into .agents/skills/cross-host-rig-commands in your project. Codex loads it when a task matches its description.
Can I use Cross Host Rig Commands in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill cross-host-rig-commands -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-host-rig-commands, .gemini/skills/cross-host-rig-commands, .github/skills/cross-host-rig-commands and .opencode/skills/cross-host-rig-commands in your project.
What does Cross Host Rig Commands need to run?
Going by SKILL.md and its folder, Cross Host Rig Commands needs credentials named REMOTE_RIG_TOKEN. Our summary lists: A credential in REMOTE_RIG_TOKEN.
Does Cross Host Rig Commands access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cross Host Rig Commands safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cross Host Rig Commands use?
Cross Host Rig Commands is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cross Host Rig Commands use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cross Host Rig Commands?
Skills that share tags, products or a category with Cross Host Rig Commands: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cross Host Rig Commands?
mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 6,551 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 10, 2026.
Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.