Proxmox Host Operator

Overview

Use this skill as an operating discipline for Proxmox work. Start with evidence, act narrowly, verify the real service state, and leave a useful operator log that another maintainer can trust.

Operating Contract

1. Identify scope before commands: host, storage, LXC/VM ID, service, user, access path, and requested outcome.
2. Run read-only diagnostics first unless the user gave an exact change request and the blast radius is already known.
3. Treat storage, backup, networking, security, migration, and secrets as high-risk surfaces.
4. Prefer one scoped change at a time, then verify before moving to the next change.
5. If an operation stalls, loops, or takes unusually long, stop and report current evidence instead of silently continuing.
6. Update the operator log, per-LXC activity log, changelog index, and relevant inventory docs after every meaningful change or incident.

Safety Rules