Use when the user wants to manage his VPS servers and the AI agents running inside them — connecting, deploying, monitoring, restarting, and operating remote hosts and their agents. Triggers on VPS, server management, remote host, SSH into server, manage my servers, agents on the server.
76
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Source of truth: ~/Documents/code/workspace/library/infrastructure.md (read it for the latest — IPs/expirations change).
| Hostname | IP | OS | Purpose | Expires |
|---|---|---|---|---|
| Ubuntu 24.04 (Dokploy) | OpenClaw — personal instance | |||
| Ubuntu 24.04 (n8n) | All n8n workflow automations (primary) | |||
| Ubuntu 24.04 | Hermes Agent — Discord gateway |
SSH as root@<IP>.
<app-login-hostname>. Build/edit workflows, no server access. Safest to share.root@<IP>. Docker, files, system config. Trusted technical people only.hpanel.hostinger.com. Billing, reboot, OS reinstall. Exposes SSH creds + browser terminal, so it grants server access too. The user only.For multi-step or exploratory work, SSH into the box first and launch the agent ON the VPS (e.g. codex --yolo), then talk to that local-on-server agent — it has full filesystem/process context and avoids fragile SSH round-trips. For short command sequences (update, config change, restart), driving an existing SSH session directly (e.g. via a cmux pane) is fine.
When checking on a remote/on-box agent, send the user one concise status line each time: what it is doing and whether it is on track.
Claude Code cmux note: after Claude finishes, it may prefill a predicted next user message; that draft is Claude, not the user speaking.
library/hermes/.hermes --version # shows version + commits behind
hermes update # auto-snapshots, updates deps, rebuilds web UI, restarts gateway itself
hermes gateway status|restart
journalctl --user -u hermes-gateway --since '5 min ago' --no-pager # gateway logs (systemd USER service)~/.hermes/config.yaml under model.provider + model.default — NOT in .env. Change via hermes model (interactive) or edit the yaml directly, then hermes gateway restart to propagate to gateways.EBADENGINE warnings during update (deps want Node >=24, box runs v22) are non-blocking — do not "fix" them.library/hermes/.66860fb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.