Skip to main content
hc
Submit
skillsFirst-partyReview first Safety · Privacy ·

Proxmox VE API Capability Pack Skill

Expert Proxmox VE API capability skill for VM/LXC lifecycle orchestration, task polling, auth safety, and cluster-aware operations.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Prerequisites

  • Proxmox API token with least-privilege scope
  • Node/cluster topology inventory
  • Backup/snapshot policy

Schema details

Install type
package
Reading time
9 min
Difficulty score
86
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
0dd1737529e1488f32e951bd9543fd8cd433619c6dc3547f266e56e8b9bb9be8
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-10
Retrieval sources
https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_APIhttps://pve.proxmox.com/wiki/Main_Pagehttps://pve.proxmox.com/pve-docs/
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Use the Proxmox VE API capability pack skill for this infrastructure operation."

# Required output
1) Endpoint and task-state mapping
2) Pre-flight and capacity checks
3) Operation sequence with stop conditions
4) Post-flight validation and rollback guidance

About this resource

Knowledge Freshness

This capability pack is pinned to documentation verified on 2026-04-10. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.

Retrieval Sources

Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.

Core Workflow

  1. Confirm target version/runtime and pull latest official docs for the task scope.
  2. Build an execution plan with explicit read-only discovery before any mutation.
  3. Validate contracts, permissions, and safety constraints before applying changes.
  4. Execute with deterministic checkpoints and rollback criteria.
  5. Produce a verification report with evidence, caveats, and next actions.

Overview

This capability pack teaches agents how to operate Proxmox VE safely and predictably through the API. It goes beyond generic automation by enforcing cluster-aware operational discipline.

Capability Scope

  • Token auth/session behavior and secure usage
  • Task lifecycle semantics and polling strategies
  • VM/LXC lifecycle orchestration patterns
  • Migration/backup/restore safety constraints
  • Failure classification and rollback protocol

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Gate write operations behind pre-flight checks.
  • Never assume synchronous completion for async tasks.
  • Validate desired state after each task completion.
  • Keep operations idempotent where possible.

Troubleshooting

Issue: API call returns success but workload state is wrong
Fix: Tie workflow completion to task result plus post-state verification.

Issue: Migration flakiness under load
Fix: Add capacity and network health gates before migration.

Issue: Permission confusion across tokens
Fix: Maintain explicit token-role matrix per workflow.

Output Contract

  1. Provide an implementation plan ordered by risk and dependency.
  2. Provide exact production-ready config/commands with no placeholders.
  3. Call out secrets, permissions, and least-privilege requirements.
  4. Include rollback and recovery guidance for each risky step.

Validation Checklist

  • Verify all referenced docs/versions before applying changes.
  • Run regression checks for core user flow and error paths.
  • Confirm observability/logging is enabled for changed components.
  • Confirm security controls (auth, rate limits, input validation) still pass.
  • Record final known limitations and follow-up actions.
Content outline
#proxmox#virtualization#api#infrastructure#capability-pack

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.