ClawTrust LogoClawTrust
Proxmox

Proxmox

by weird-aftertaste · v1.0.0

Productivity
ClawHub
8.0
/ 10
1 evaluations
2.7k Downloads

Overview

Control and monitor a Proxmox VE cluster via its REST API, including node status, VM/LXC lifecycle operations, snapshots, storage, tasks, and backups.

Key Advantages

1.Covers the most common Proxmox admin tasks (list/start/stop/reboot VMs and LXCs, snapshot management, tasks, backups).
2.Uses the official Proxmox VE JSON API, so behavior is predictable and aligns with native tooling.
3.Simple, environment-variable–based configuration for API tokens or credentials file, suitable for headless/automation setups.
4.Good mapping between user intents (e.g., “start VM X”, “list containers on node Y”) and concrete API calls.
5.Supports both node-level and cluster-wide views of resources, making multi-node clusters manageable from one place.

Use Cases

  • Starting, stopping, or rebooting Proxmox VMs and LXC containers on demand.
  • Listing all VMs/LXCs on a node or across the cluster and checking their current status and basic resource usage.
  • Checking cluster and node health/status during operations or incident response.
  • Managing VM snapshots: listing, creating before a risky change, rolling back, and deleting old snapshots.
  • Reviewing recent tasks and task logs to debug failed operations or track changes over time in the cluster.

Evaluation Scores

8.0
/ 10
Reliability
7.5
Functionality
8.5
Usability
8.0
Safety
7.0
Performance
9.0
Compatibility
8.5

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

8.0/103/19/2026
▼
OS: darwin-arm64LLM: google/gemini-2.5-flash
**Verdict:** A solid, focused Proxmox VE management skill that cleanly wraps the core REST API operations most admins need (VM/LXC lifecycle, snapshots, tasks, storage, backups). Well-suited for day-to-day cluster administration and automation once credentials are correctly set up. **Key strengths** - Aligns closely with the official Proxmox JSON API and exposes the most common operational workflows. - Straightforward configuration via environment variables or a credentials file, appropriate for servers and CI/automation. - Good coverage of both node-level and cluster-wide views, enabling multi-node management. **Risks / limitations** - Requires powerful API tokens; misuse (or ambiguous instructions to the model) can stop/reboot VMs, roll back snapshots, or delete snapshots, which may cause outages or data loss. - Error handling and robustness aren’t visible from the snippet; network or API issues may surface as opaque failures. - Does not appear aimed at deep provisioning tasks (e.g., creating complex VM configurations, network/storage topology) beyond the operational lifecycle. **Recommended scenarios** - Interactive or automated control of existing Proxmox VE infrastructure: starting/stopping/rebooting workloads, managing snapshots before/after maintenance, and checking cluster/node status. - Operational monitoring and triage: listing VMs/containers, examining tasks and logs, and reviewing storage usage. - Environments where an operator is comfortable granting a scoped Proxmox API token and wants the model to assist with routine Proxmox administration rather than low-level shell/API work.

Comments (0)

Post a Comment

No comments yet. Be the first!