Install command
Provided
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.
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Source URLs
- https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_API, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/proxmox-ve-api-capability-pack.mdx
- Package URL
- /downloads/skills/proxmox-ve-api-capability-pack.zip
- Package SHA256
- 0dd1737529e1488f32e951bd9543fd8cd433619c6dc3547f266e56e8b9bb9be8
- Safety notes
- Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions., Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
- Privacy notes
- Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots., Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
- Platform compatibility
- claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
- Author
- JSONbored
- Claim status
- unclaimed
- Last verified
- 2026-04-10
Decision playbook
Ready to evaluate for your workflow
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
Compare context
Selected
0
Current score
96
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
CompleteConfirm ownership and provenance before trusting install instructions.
- Done
Source link availableRequired
Open the canonical repository and verify ownership.
- Done
Source provenance statusRequired
Marked as first-party.
- Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Safety and privacy checks
CompleteValidate risk disclosures before installation or API wiring.
- Done
Safety notes presentRequired
Review the listed safety guidance before running commands.
- Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
- Done
Trust level risk gateRequired
Trust level does not block evaluation.
Package and install checks
CompleteCheck package metadata and artifact integrity signals.
- Done
Install payload available
Install or copy payload is available for review.
- Done
Package verification flag
Package marked verified.
- Done
Checksum metadata
SHA-256 hash is present.
Compare-driven decision checks
Needs reviewUse compare context to validate trade-offs before adoption.
- Pending
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
- Pending
Baseline comparison available
No baseline peer selected yet.
- Pending
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Package install
Copy-ready — paste the snippet to get started.
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
3 to clear
Platforms
6 listed
Difficulty
86/100
Adoption plan
Balanced adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Pre-adoption checks
Validate source and review signals before any execution.
- Done
Confirm source provenanceRequired
Source URL/provenance metadata is present.
- Done
Confirm metadata review state
Listing has review metadata.
- Done
Verify install payload
Install/config payload exists and can be inspected.
Security checks
Confirm safety, privacy, and package integrity signals.
- Done
Review safety notesRequired
Safety notes are present.
- Done
Review privacy notesRequired
Privacy notes are present.
- Done
Verify package integrity metadata
Package verification/checksum metadata is available.
Rollout
Adopt in controlled steps based on the selected plan.
- Pending
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
- Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
- Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Evidence readiness matrix · balanced
Required evidence gates are covered (6/6 signals complete).
Source provenance
PresentSource repository/provenance is listed.
Required in this preset
Metadata review
PresentReview metadata is present.
Required in this preset
Safety notes
PresentSafety notes are present.
Required in this preset
Privacy notes
PresentPrivacy notes are present.
Optional in this preset
Package integrity
PresentPackage integrity metadata is present.
Optional in this preset
Install payload
PresentInstall payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
Decision timeline · balanced
6/6 steps complete with no blocking gaps for this preset.
triage
Confirm source provenanceRequired
Source/provenance metadata is available.
triage
Check metadata review statusRequired
Review metadata is available.
verify
Review safety notesRequired
Safety notes are available.
verify
Review privacy notes
Privacy notes are available.
verify
Validate package integrity metadata
Package integrity metadata is available.
rollout
Verify install payload and commandsRequired
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
Prerequisite readiness
3 prerequisites to line up before setup. Have accounts and credentials ready first.
Account & credentials1General2
Safety & privacy surface
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.
- SafetyExecution & processesCan design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
- SafetyCredentials & tokensKeep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
- PrivacyData retentionInputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
- PrivacyCredentials & tokensRedact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Safety notes
- Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
- Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
- Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
- Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
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
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.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 guidanceAbout 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
- https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_API
- https://pve.proxmox.com/wiki/Main_Page
- https://pve.proxmox.com/pve-docs/
Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.
Core Workflow
- Confirm target version/runtime and pull latest official docs for the task scope.
- Build an execution plan with explicit read-only discovery before any mutation.
- Validate contracts, permissions, and safety constraints before applying changes.
- Execute with deterministic checkpoints and rollback criteria.
- 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.mdcontent as reusable workflow instructions.
Manual Adaptation
- Gemini CLI: native skill usage via
.gemini/skills/<skill-name>/SKILL.mdor.agents/skills/<skill-name>/SKILL.mdwhere supported. - Cursor: use the generated
.cursor/rules/*.mdcadapter 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
- Provide an implementation plan ordered by risk and dependency.
- Provide exact production-ready config/commands with no placeholders.
- Call out secrets, permissions, and least-privilege requirements.
- 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.
Source citations
Add this badge to your README
Show that Proxmox VE API Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/proxmox-ve-api-capability-pack)How it compares
Proxmox VE API Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Expert Proxmox VE API capability skill for VM/LXC lifecycle orchestration, task polling, auth safety, and cluster-aware operations. Open dossier | Orchestrate Proxmox VM and LXC lifecycle operations via API with safe sequencing, capacity checks, and rollback-aware automation. Open dossier | Deep, version-pinned Unraid API capability skill covering auth, schema patterns, safe mutations, and operational automation design. Open dossier | Expert dynamic workflows capability pack applying documented /workflows monitoring, scoped orchestration prompts, and keyword trigger governance from official workflows documentation. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-10 | Package verified2026-04-10 | Package verified2026-04-10 | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | No submission link | Submission linkedSource submission |
| SubmitterDiffers | — | — | — | kiannidev |
| Install risk | Review first | Low risk | Low risk | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | skills | skills | skills | skills |
| Source | first-party | first-party | first-party | source-backed |
| Author | JSONbored | JSONbored | JSONbored | kiannidev |
| Added | 2026-04-10 | 2026-04-10 | 2026-04-10 | 2026-06-16 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions. Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution. | ✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions. Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution. | ✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions. Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution. | ✓Autonomous workflows can run shell commands without mid-run user input—scope paths and tools first. Do not enable destructive automation without explicit approval gates. Review outputs as draft until a human validates evidence. |
| Privacy notes | ✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots. Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts. | ✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots. Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts. | ✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots. Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts. | ✓Workflow and session output may contain proprietary code and credentials. Summaries for external channels require redaction. |
| Prerequisites |
|
|
|
|
| Install | | | | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related guides
Source-backed guides for putting this to work.
Featured in
Signals
Loading live community signals…
More like this, weekly
A short, calm digest of reviewed Claude resources. Unsubscribe any time.