hermes-proxmox-multihost: one skill, N standalone Proxmox servers

Most home-lab Proxmox tooling assumes one cluster. Reality for a lot of us is several standalone servers, accumulated over the years, each with its own login, its own quirks, and no interest in joining anybody’s cluster. This skill — built on danielbitpro/hermes-proxmox-control, extended with a host registry and a multi-host helper — lets one Hermes Agent session manage all of them.

The part I’m proudest of is the failure model: get_all() wraps each connection in its own try/except, so when pve3 is down for maintenance, listing VMs across the fleet returns results from pve1 and pve2 plus a clean error line for pve3 — not a crash. Secrets resolve through Bitwarden Secrets Manager by UUID at call time; the registry on disk maps hostnames to secret IDs and never stores a credential itself.

Features:

• VM/CT inventory, status, config inspection across 3+ independent hosts
• Power management (start/shutdown/stop/reboot) and snapshots — create, list, rollback, delete
• Resource monitoring per node and per VM; storage management; template cloning
• Fan-out operations across all hosts with per-host fault tolerance — one dead node never aborts the batch
• BWSM-backed secrets (bwsm UUID references), with env-var fallback; plaintext discouraged and warned
• State-changing operations gated behind a documented safety checklist (references/operations.md)
• Verified proxmoxer gotchas documented: eager password auth vs lazy token auth, correct token kwargs, ACL requirements
• Smoke-testable read-only before you let an agent anywhere near a power button

Credits where due: Daniel’s original single-host skill, Magnus’s SkillOpt methodology used to harden the docs. Source: github.com/rahlquist/hermes-proxmox-multihost · MIT licensed.