proxmox-ve-operations

Operate, inspect, maintain, back up, restore, and safely evolve Proxmox VE 9 nodes, storage, networking, LXC, and VMs using official-first guidance. Use for Proxmox node administration, guest lifecycle, storage, network, package updates, backup/restore, upgrade planning, API/CLI inspection, and third-party helper-script review.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, operationally precise skill body with a strong validated workflow and good progressive-disclosure signaling. Its main weakness is the missing templates/proxmox-operation-plan.md referenced in two places, plus minor verbosity.

Suggestions

Add the missing templates/proxmox-operation-plan.md (or remove the two references to it) so the plan step and Bundled resources section point to a real file.

Tighten consequence-explaining sentences in Storage and backup (e.g. the thin-provisioning warning) to rely more on Claude's existing knowledge and reduce token weight.

Surface a couple of representative inline command examples in the body (or a one-line pointer to the cookbook section) so core actions are actionable without requiring a reference hop.

Dimension	Reasoning	Score
Conciseness	The body is dense, operational, and largely assumes Claude's competence (it does not explain what a VM or LXC is), but several consequence-explaining clauses (e.g. "Thin provisioning can overcommit capacity; a full storage can cause guest I/O errors and data corruption") and hedging language could be trimmed slightly.	4 / 5
Actionability	Names concrete tooling (pvesh, pvesm, pct, qm, pveversion) and points to real reference files and a read-only audit script, but step 4 and the Bundled resources section direct the reader to use templates/proxmox-operation-plan.md, a file that does not exist in the bundle.	4 / 5
Workflow Clarity	The seven-step Operating workflow is clearly sequenced (Classify, Inspect, Select boundary, Plan, Obtain confirmation, Execute minimally, Validate and document) with explicit confirmation and validation checkpoints for destructive and state-changing operations, satisfying the destructive-ops feedback-loop requirement.	5 / 5
Progressive Disclosure	The body is a clean overview with a dedicated Bundled resources section signaling one-level-deep references to references/ and scripts/, which exist; however the referenced templates/proxmox-operation-plan.md is missing, a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality, third-person description that clearly states capabilities and explicit use-conditions for Proxmox VE 9 operations. It is comprehensive and distinctive, with only minor trigger-term gaps.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Operate, inspect, maintain, back up, restore, and safely evolve") across named domains ("nodes, storage, networking, LXC, and VMs"), giving comprehensive coverage of capabilities rather than vague language.	5 / 5
Completeness	Explicitly answers both what ("Operate, inspect, maintain, back up, restore, and safely evolve Proxmox VE 9...") and when ("Use for Proxmox node administration, guest lifecycle, storage, network, package updates, backup/restore, upgrade planning, API/CLI inspection, and third-party helper-script review.") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural-term coverage ("Proxmox node administration, guest lifecycle, storage, network, package updates, backup/restore, upgrade planning, API/CLI inspection, and third-party helper-script review"), but a few common user phrasings (e.g. "create a VM/container", standalone "LXC container") are absent, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Proxmox VE 9 platform operations) with distinct, domain-specific triggers, so it is unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: pvnkmnk/AgenticSelfHostSkills
Path: skills/proxmox-ve-operations/SKILL.md
Commit: 0f62e6b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.