← Back to Skills Marketplace

Proxmox VE Manager

Name: Proxmox VE Manager
Author: pratiknarola

by Pratik Narola · GitHub ↗ · v1.0.0 · MIT-0

cross-platform ✓ Security Clean

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install proxmox-manager

Description

Manage Proxmox VE clusters via REST API. Use when user asks to list, start, stop, restart VMs or LXC containers, check node status, create snapshots, view ta...

README (SKILL.md)

Proxmox VE Management

Configuration

Set environment variables or store in ~/.proxmox-credentials:

# Option 1: API Token (recommended)
export PROXMOX_HOST="https://192.168.1.100:8006"
export PROXMOX_TOKEN_ID="user@pam!tokenname"
export PROXMOX_TOKEN_SECRET="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

# Option 2: Credentials file
cat > ~/.proxmox-credentials \x3C\x3C 'EOF'
PROXMOX_HOST=https://192.168.1.100:8006
PROXMOX_TOKEN_ID=user@pam!monitoring
PROXMOX_TOKEN_SECRET=your-token-secret
EOF
chmod 600 ~/.proxmox-credentials

Create API token in Proxmox: Datacenter → Permissions → API Tokens → Add

CLI Usage

# Load credentials
source ~/.proxmox-credentials 2>/dev/null

# Auth header for API token
AUTH="Authorization: PVEAPIToken=$PROXMOX_TOKEN_ID=$PROXMOX_TOKEN_SECRET"

Common Operations

Cluster & Nodes

# Cluster status
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/cluster/status" | jq

# List nodes
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes" | jq '.data[] | {node, status, cpu, mem: (.mem/.maxmem*100|round)}'

# Node status
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/status" | jq

List VMs & Containers

# All VMs on a node
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu" | jq '.data[] | {vmid, name, status, mem: .mem, cpu: (.cpu*100|round)}'

# All LXC containers on a node
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/lxc" | jq '.data[] | {vmid, name, status}'

# Cluster-wide resources
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/cluster/resources?type=vm" | jq '.data[] | {node, vmid, name, type, status}'

VM/Container Control

# Start VM
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/status/start"

# Stop VM
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/status/stop"

# Shutdown VM (graceful)
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/status/shutdown"

# Reboot VM
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/status/reboot"

# Same for LXC: replace /qemu/ with /lxc/

Snapshots

# List snapshots
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/snapshot" | jq

# Create snapshot
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/snapshot" \
  -d "snapname=snap1" -d "description=Before update"

# Rollback
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/snapshot/{snapname}/rollback"

# Delete snapshot
curl -ks -X DELETE -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/qemu/{vmid}/snapshot/{snapname}"

Tasks & Logs

# Recent tasks
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/tasks" | jq '.data[:10] | .[] | {upid, type, status, user}'

# Task log
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/tasks/{upid}/log" | jq -r '.data[].t'

Storage

# List storage
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/storage" | jq '.data[] | {storage, type, active, used_fraction: (.used/.total*100|round|tostring + "%")}'

# Storage content
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/storage/{storage}/content" | jq

Backups

# List backups
curl -ks -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/storage/{storage}/content?content=backup" | jq

# Start backup
curl -ks -X POST -H "$AUTH" "$PROXMOX_HOST/api2/json/nodes/{node}/vzdump" \
  -d "vmid={vmid}" -d "storage={storage}" -d "mode=snapshot"

Helper Script

Use scripts/pve.sh for common operations:

./scripts/pve.sh status          # Cluster overview
./scripts/pve.sh vms             # List all VMs
./scripts/pve.sh start {vmid}    # Start VM
./scripts/pve.sh stop {vmid}     # Stop VM

Notes

Replace {node}, {vmid}, {storage}, {snapname} with actual values
API tokens don't need CSRF tokens for POST/PUT/DELETE
Use -k to skip SSL verification for self-signed certs
Task operations return UPID for tracking async jobs

Usage Guidance

Install only if you want an agent to help manage Proxmox infrastructure. Use a least-privilege Proxmox API token, store it carefully, and require explicit user approval before running stop, reboot, rollback, delete, or backup commands against production systems.

Capability Assessment

ℹ Purpose & Capability

The documented capabilities match the stated purpose of managing Proxmox VE clusters, including read operations and VM/container lifecycle actions. Snapshot rollback, snapshot deletion, and backup initiation are high-impact but still related to Proxmox administration.

ℹ Instruction Scope

Commands are shown explicitly and require user-provided targets, but the skill does not add confirmation guidance for disruptive actions such as force stop, reboot, rollback, or snapshot deletion.

✓ Install Mechanism

The package contains a markdown skill file and one helper shell script. There is no installer, dependency bootstrap, auto-execution hook, or hidden setup behavior.

ℹ Credentials

Use of Proxmox host and API token environment variables is proportionate for REST API management. The documentation sets chmod 600 for a credentials file, but gives limited broader secret-handling guidance.

ℹ Persistence & Privilege

The only persistence described is an optional local ~/.proxmox-credentials file. The skill does not create background services, scheduled tasks, or durable agent behavior, but stored API tokens may have broad administrative impact depending on Proxmox permissions.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install proxmox-manager
After installation, invoke the skill by name or use /proxmox-manager
Provide required inputs per the skill's parameter spec and get structured output

Version History

v1.0.0

Initial release: Proxmox VE cluster management via REST API with helper scripts

Metadata

Slug proxmox-manager

Version 1.0.0

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 1

Frequently Asked Questions

What is Proxmox VE Manager?

Manage Proxmox VE clusters via REST API. Use when user asks to list, start, stop, restart VMs or LXC containers, check node status, create snapshots, view ta... It is an AI Agent Skill for Claude Code / OpenClaw, with 27 downloads so far.

How do I install Proxmox VE Manager?

Run "/install proxmox-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Proxmox VE Manager free?

Yes, Proxmox VE Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Proxmox VE Manager support?

Proxmox VE Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Proxmox VE Manager?

It is built and maintained by Pratik Narola (@pratiknarola); the current version is v1.0.0.

More Skills