skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
davidondrej/skills60 installs

vps-server-management

Use when the user wants to manage their 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.

How do I install this agent skill?

npx skills add https://github.com/davidondrej/skills --skill vps-server-management
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides instructions for managing VPS infrastructure and orchestrating AI agents on remote servers. It promotes high-privilege operations and identifies local files containing sensitive infrastructure metadata.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

VPS Server Management

Source of truth: ~/infrastructure.md (read it for the latest — IPs/expirations change).

Servers (Hostinger VPS) — 3 total

HostnameIPOSPurposeExpires
personal.openclaw<IP>Ubuntu 24.04 (Dokploy)OpenClaw — personal instance<redacted>
n8n.automations<IP>Ubuntu 24.04 (n8n)All n8n workflow automations (primary)<redacted>
private.hermes<IP>Ubuntu 24.04Hermes Agent — Discord gateway<redacted>

SSH as root@<IP>.

Access levels (never share higher than needed)

  1. App login — e.g. <app-login-url>. Build/edit workflows, no server access. Safest to share.
  2. VPS SSH — root@<IP>. Docker, files, system config. Trusted technical people only.
  3. Hostinger hPanel — hpanel.hostinger.com. Billing, reboot, OS reinstall. Exposes SSH creds + browser terminal, so it grants server access too. The user 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 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.

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.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.
  • npm EBADENGINE warnings 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/.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/davidondrej/skills/vps-server-management">View vps-server-management on skillZs</a>