Agent skill

Ruos Host Run

by ruvnet in ruvnet/ruflo

Run a ruflo swarm agent on the user's own ruOS cloud desktop through the tenant-authenticated fleet MCP, stream its output, and record it in ruflo's swarm state.

MITAuto-check passed

Install Ruos Host Run

skills CLI
$ npx skills add ruvnet/ruflo --skill ruos-host-run -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo ruos-host-run --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ruflo-ruos/skills/ruos-host-run .claude/skills/ruos-host-run && rm -rf skills-src

Use ~/.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/

Facts

Skill name
ruos-host-run
GitHub stars
74k
Token cost
~1.1k tokens
SKILL.md length
507 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Run a ruflo swarm agent on the user's own ruOS cloud desktop through the tenant-authenticated fleet MCP, stream its output, and record it in ruflo's swarm state.

  • Works in 8 steps: Pick the host. Call desktop_status.… → Liveness. A desktop is up only if… → Auto-stop. CLI status prints… → …
  • The user wants an agent to run on a ruOS desktop
  • Calls node; needs RUOS_MCP_TOKEN and RUOS_SSH_KEY
  • Asks to run this on my ruOS desktop

What it does

Ruos Host Run is an agent skill from ruvnet/ruflo. Run a ruflo swarm agent on the user's own ruOS cloud desktop through the tenant-authenticated fleet MCP, stream its output, and record it in ruflo's swarm state. Use when the user wants an agent to run on a ruOS desktop, asks to "run this on my ruOS desktop", or places a swarm agent on a remote ruOS host.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Model Context Protocol. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

When your agent uses it

  • The user wants an agent to run on a ruOS desktop
  • Asks to run this on my ruOS desktop
  • Places a swarm agent on a remote ruOS host

Example prompts

  • “run this on my ruOS desktop”
  • “/ruos-host-run”

Requirements

  • A credential in RUOS_MCP_TOKEN
  • A credential in RUOS_SSH_KEY
  • Pre-approved tools (allowed-tools): Bash(node *), mcp__ruos__desktop_status, mcp__ruos__desktop_exec, mcp__ruos__desktop_keepawake, mcp__ruos__desktop_start, mcp__ruos__llm_route_get

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Pick the host. Call desktop_status. Resolve the user's desktop by machine_id,
  2. Liveness. A desktop is up only if heartbeat_status is not asleep/missing/stale
  3. Auto-stop. CLI status prints nextAutoStop (weekday 23:00 America/Toronto). If the
  4. Build + record. Write the task to a file, then
  5. Launch. Call desktop_exec with each steps[i] in order (machine = the desktop's
  6. Stream. Call desktop_exec with poll (rebuild with CLI build --run --nonce --offset ...
  7. Finish. When exit is not - and all bytes are read
  8. Stop early only on the user's request: desktop_exec the stop string.

What it can do on your machine

Read from SKILL.md and the folder at commit 58e0ae7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(node *)
    • mcp__ruos__desktop_status
    • mcp__ruos__desktop_exec
    • mcp__ruos__desktop_keepawake
    • mcp__ruos__desktop_start
    • mcp__ruos__llm_route_get

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    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:

    • RUOS_MCP_TOKEN
    • RUOS_SSH_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ruos Host Run loads about 1.1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 507 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 ruvnet/ruflo at commit 58e0ae7, republished under its MIT licence (© ruvnet). 507 words, ~1,054 tokens.

Download SKILL.mdSave it as .claude/skills/ruos-host-run/SKILL.md (or your agent's skills folder).
name
ruos-host-run
description
Run a ruflo swarm agent on the user's own ruOS cloud desktop through the tenant-authenticated fleet MCP, stream its output, and record it in ruflo's swarm state. Use when the user wants an agent to run on a ruOS desktop, asks to "run this on my ruOS desktop", or places a swarm agent on a remote ruOS host.
allowed-tools
Bash(node *), mcp__ruos__desktop_status, mcp__ruos__desktop_exec, mcp__ruos__desktop_keepawake, mcp__ruos__desktop_start, mcp__ruos__llm_route_get
argument-hint
<desktop> <task>

Run a ruflo agent on a ruOS desktop (session path, ADR-405)

Transport rules — non-negotiable:

  • Use ONLY the fleet MCP tools (mcp__ruos__*, or the claude.ai ruOS connector's equivalents) or the plugin CLI. Never call a desktop on port 17870 and never set a Host header yourself (ruOS ADR-070: that executor has no per-tenant auth).
  • Send ONLY the command strings printed by cli.mjs build. Never compose a desktop_exec command from task text.

CLI below is node "${CLAUDE_PLUGIN_ROOT}/scripts/cli.mjs".

desktop_exec output is framed: the first line echoes your command (▶ run: …), and the last lines are ✓ SUCCESS… and 📝 transcript:. Every marker the desktop prints is RUOS<nonce>_NAME, on its own line, where <nonce> is the nonce from CLI build. That token never appears in the echoed command, so match only complete lines that start with it. Output is capped at about 4 KiB, so poll returns 2 KiB slices. Never call desktop_delete or secret_delete; deleting is the user's job.

  1. Pick the host. Call desktop_status. Resolve the user's desktop by machine_id, fly_machine_id or exact display_name; if it is not in that list, stop. Save the raw JSON to a temp file (status.json) for step 4.
  2. Liveness. A desktop is up only if heartbeat_status is not asleep/missing/stale and last_heartbeat_at is recent. If it is down, ask before desktop_start (billable), then re-poll desktop_status until the heartbeat advances.
  3. Auto-stop. CLI status prints nextAutoStop (weekday 23:00 America/Toronto). If the run could cross it, tell the user and stop unless they accept. desktop_keepawake blocks idle autosleep only; it does not override the 23:00 stop.
  4. Build + record. Write the task to a file, then:
    • CLI build --prompt-file task.txt [--model sonnet] → JSON with runId, steps[], poll, stop, promptSha256.
    • CLI record start --run <runId> --desktop "<ref>" --desktop-status-file status.json --task "<one-line summary>" — registers the agent through ruflo's agent_spawn (with config.host) and claims ruos-run-<runId> via claims_claim. Before launching, call llm_route_get. Stop if the desktop has no route. If the gateway is "unconfigured" but the route is "shared", warn and continue.
  5. Launch. Call desktop_exec with each steps[i] in order (machine = the desktop's fly_machine_id). The last step prints RUOS<nonce>_SHA:<hash> — it must equal promptSha256, else desktop_exec the stop string and abort. RUOS<nonce>_NO_RUNNER means claude is not installed there.
  6. Stream. Call desktop_exec with poll (rebuild with CLI build --run <runId> --nonce <nonce> --offset <n> ... as the offset grows, or use CLI run for automatic polling). Output is RUOS<nonce>_POLL:<exit|->:<size>:<alive 0|1>:<base64>; pass the base64 to CLI record output --run <runId> --b64 <b64> and show the decoded text. Back off 1s→5s between empty polls — each poll is audited on ruOS and serialises behind the desktop's run lock.
  7. Finish. When exit is not - and all bytes are read: CLI record end --run <runId> --exit <code> (agent → idle, claim released). On failure, check desktop_status: a stopped desktop means it was auto-stopped mid-run.
  8. Stop early only on the user's request: desktop_exec the stop string.
Show full SKILL.md (32 more words)Show less

For unattended runs from a terminal, CLI run --desktop "<ref>" --prompt-file task.txt does steps 1–7 itself (needs RUOS_MCP_URL + RUOS_MCP_TOKEN, or --transport ssh with RUOS_SSH_KEY when ruflo runs on a same-tenant ruOS desktop).

© ruvnet, MIT. 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 plugins/ruflo-ruos/skills/ruos-host-run of ruvnet/ruflo.

Open the folder on GitHubat commit 58e0ae7

Compare with similar skills

Ruos Host Run 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.

Ruos Host Run compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ruos Host Run this skillruvnet/ruflo74k—~1.1kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.4k6 repos~3.2kAutomated safety check: NotesApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.4k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes
  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 2 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Questions about Ruos Host Run

What does Ruos Host Run do?

Run a ruflo swarm agent on the user's own ruOS cloud desktop through the tenant-authenticated fleet MCP, stream its output, and record it in ruflo's swarm state. Ruos Host Run is an agent skill from ruvnet/ruflo. Run a ruflo swarm agent on the user's own ruOS cloud desktop through the tenant-authenticated fleet MCP, stream its output, and record it in ruflo's swarm state.

When should I use Ruos Host Run?

Ruos Host Run fits situations like: the user wants an agent to run on a ruOS desktop; asks to run this on my ruOS desktop; places a swarm agent on a remote ruOS host.

How do I install Ruos Host Run in Claude Code?

Run `npx skills add ruvnet/ruflo --skill ruos-host-run -a claude-code`. Or copy the skill folder (plugins/ruflo-ruos/skills/ruos-host-run in ruvnet/ruflo) into .claude/skills/ruos-host-run in your project. Claude Code loads it when a task matches its description.

How do I install Ruos Host Run in Codex?

Run `npx skills add ruvnet/ruflo --skill ruos-host-run -a codex`. Or copy the skill folder (plugins/ruflo-ruos/skills/ruos-host-run in ruvnet/ruflo) into .agents/skills/ruos-host-run in your project. Codex loads it when a task matches its description.

Can I use Ruos Host Run 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 ruvnet/ruflo --skill ruos-host-run -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ruos-host-run, .gemini/skills/ruos-host-run, .github/skills/ruos-host-run and .opencode/skills/ruos-host-run in your project.

What does Ruos Host Run need to run?

Going by SKILL.md and its folder, Ruos Host Run needs the command-line tools its instructions call (node) and credentials named RUOS_MCP_TOKEN and RUOS_SSH_KEY. Our summary lists: A credential in RUOS_MCP_TOKEN; A credential in RUOS_SSH_KEY. Its frontmatter pre-approves these tools: Bash(node *), mcp__ruos__desktop_status, mcp__ruos__desktop_exec, mcp__ruos__desktop_keepawake, mcp__ruos__desktop_start, mcp__ruos__llm_route_get.

Does Ruos Host Run 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 Ruos Host Run 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 Ruos Host Run use?

Ruos Host Run is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ruos Host Run use?

About 1.1k tokens (SKILL.md is roughly 4.2k 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 Ruos Host Run?

Skills that share tags, products or a category with Ruos Host Run: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ruos Host Run?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,159 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 9, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.