// Use when bootstrapping an SSH-accessible Ubuntu/Debian VPS with the Agent Control Room template, core agent tooling, and linked control-room skills.
| name | setup-control-room |
| description | Use when bootstrapping an SSH-accessible Ubuntu/Debian VPS with the Agent Control Room template, core agent tooling, and linked control-room skills. |
Use this skill to turn an SSH-accessible VPS into a tooled Agent Control Room box.
It installs core tools, clones the Agent Control Room template, and links bundled skills.
/setup-control-roomSSH_ALIAS: required unless discoverable from local SSH config.CONTROL_ROOM_PATH: default /root/agent-control-room.CONTROL_ROOM_REPO: default https://github.com/shannhk/hermes-agent-control-room.git.Before running:
ssh <alias> works.If SSH does not work, stop and tell the user to create/fix the VPS first.
ssh -o ConnectTimeout=10 <alias> 'echo connected as $(whoami) on $(hostname); lsb_release -a'
Copy assets/bootstrap.sh to the VPS.
Run the bootstrap script:
ssh <alias> '/tmp/bootstrap-control-room.sh' 2>&1 | tee /tmp/control-room-bootstrap.log
curl, ca-certificates, git, tmux, htop/root/agent-control-room~/.claude/skillsThose are intentionally left for the user or a later agent setup flow.
After bootstrap, tell the user:
ssh <alias>
claude /login
codex
hermes
cd /root/agent-control-room
cat README.md
Also remind them that interactive auth should happen in a real SSH terminal.
Use when creating a fresh Hetzner Cloud VPS with an SSH alias, local project folder, provisioning script, destroy script, and optional handoff into setup-control-room.
Use when designing, auditing, or documenting backups for Hermes agents without committing secrets.
Use when managing the Agent Control Room: documenting Hermes agents, adding agent folders, updating runbooks, checking architecture, mapping env vars without values, or keeping the control room source of truth consistent.
Use when creating, updating, validating, or explaining the agent registry for a Hermes Agent Control Room.
Use when auditing a VPS-based Hermes agent setup for exposed dashboards, weak secret handling, broad keys, Docker risks, or missing backup/security documentation.
Use when an orchestrator needs to route work to specialist Hermes agents through a task bus, create task briefs, check outboxes, or summarize delegated results.