Vps server management
Use when David 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.From its SKILL.md
npx -y skills add adriannoes/awesome-agentic-ai --skill vps-server-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.9 KB, 721 tokens by cl100k_base, as published. Nobody here has run it
VPS Server Management
Source of truth: <path-to-infrastructure-doc>/infrastructure.md (read it for the latest — IPs/expirations change).
Servers (Hostinger VPS) — 3 total
| Hostname | IP | OS | Purpose | Expires |
|---|---|---|---|---|
| personal.openclaw | <IP-1> | Ubuntu 24.04 (Dokploy) | OpenClaw — personal instance | <expiry-date> |
| n8n.automations | <IP-2> | Ubuntu 24.04 (n8n) | All n8n workflow automations (primary) | <expiry-date> |
| private.hermes | <IP-3> | Ubuntu 24.04 | Hermes Agent — Discord gateway | <expiry-date> |
SSH as root@<IP>.
Access levels (never share higher than needed)
- App login — e.g.
<n8n-app-hostname>. Build/edit workflows, no server access. Safest to share. - VPS SSH —
root@<IP>. Docker, files, system config. Trusted technical people only. - Hostinger hPanel —
hpanel.hostinger.com. Billing, reboot, OS reinstall. Exposes SSH creds + browser terminal, so it grants server access too. David only.
Managing a VPS via an agent
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 David 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 David speaking.
Agents on servers
- OpenClaw → personal.openclaw (managed via Dokploy).
- Hermes → private.hermes (Discord gateway). Setup/config docs in
library/hermes/. - n8n → n8n.automations.
Hermes ops (on private.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)
- Default model lives in
~/.hermes/config.yamlundermodel.provider+model.default— NOT in.env. Change viahermes model(interactive) or edit the yaml directly, thenhermes gateway restartto propagate to gateways. - npm
EBADENGINEwarnings during update (deps want Node >=24, box runs v22) are non-blocking — do not "fix" them. - Deeper docs (Discord/Slack/WhatsApp setup, file structure, vision config):
library/hermes/.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.