AI assistants

An AI assistant that can run shell commands can use cv4pve-cli to read and operate a Proxmox VE cluster: it discovers the API with api ls and api usage, reads JSON with -o json, and needs no SSH access to the nodes.

The cv4pve-cli skill

The repository ships a skill, skills/cv4pve-cli/SKILL.md: a short file in the Agent Skills format that Claude Code, Codex and other assistants load when a request matches its description. It tells the assistant to:

• leave the contexts alone and read with -o json;
• explore the API with alias list --search, api ls and api usage -v;
• run every change first with --dry-run, and for real only after you agree, adding --yes where needed.

Install it with the skills command, which needs Node.js:

npx skills add Corsinvest/cv4pve-cli

Or copy the file into the skills folder of your assistant: .claude/skills/ for Claude Code,.agents/skills/ for Codex, in the project or under your home folder:

mkdir -p .claude/skills/cv4pve-cli
curl -fL -o .claude/skills/cv4pve-cli/SKILL.md https://raw.githubusercontent.com/Corsinvest/cv4pve-cli/master/skills/cv4pve-cli/SKILL.md

Give it a token of its own

The skill tells the assistant what to do; the token decides what it can do. cv4pve-cli asks --yes only for the aliases that cannot be undone; api calls and the other aliases run at once (see Operations that change the cluster), and the skill cannot prevent that. Create a context for the assistant with a token of its own: PVEAuditor if it only reads, otherwise a role with only the operations you want it to run, on the pool or the guests concerned. See Permissions.

cv4pve-cli must be able to write in ~/.cv4pve/, where it keeps the contexts and the API schema cache: an assistant that runs in a sandbox needs that folder allowed. In Git Bash on Windows it also needs MSYS_NO_PATHCONV=1 (see Git Bash on Windows). The settings a user needed for Claude Code on macOS and for Codex are in issue #10.