Proxmox

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 tasks, or manage Proxmox infrastructure. Requires API token or credentials configured.

This skill's functionality matches its description (it talks to the Proxmox API), but the package metadata is incomplete. Before installing or running it: - Inspect scripts/pve.sh yourself (already included) and verify you are comfortable running it. - Provide credentials only as a Proxmox API token with minimal privileges (create a token scoped only to the operations you need). Do not use full root/password if unnecessary. - The skill expects PROXMOX_HOST, PROXMOX_TOKEN_ID, and PROXMOX_TOKEN_SECRET, and the system needs curl and jq — but the registry metadata does not declare these. Ensure those env vars/binaries are present and documented where you manage skills. - Avoid using -k/--insecure in production; instead configure TLS properly or use a token over a trusted connection. - Consider running first in a restricted test environment and limit the API token privileges (least privilege). If you need the skill to be allowed to run autonomously, treat that as higher risk and audit token scopes and logs. If the publisher can update the skill metadata to declare the required env vars and binaries, and remove or document the use of -k, the package will be much more coherent and easier to trust.

Type: OpenClaw Skill Name: proxmox Version: 1.0.1 The skill bundle is benign. It provides functionality to manage Proxmox VE clusters via its REST API, as described in SKILL.md. The `scripts/pve.sh` script correctly implements these operations, loading credentials from `~/.proxmox-credentials` or environment variables and making API calls exclusively to the user-configured Proxmox host. There is no evidence of data exfiltration to unauthorized endpoints, malicious execution, persistence mechanisms, prompt injection attempts against the agent, or obfuscation. The use of `curl -k` (insecure SSL) is noted but is a common practice for Proxmox with self-signed certificates and is explicitly mentioned in the documentation, not indicative of malicious intent.