CtrlK
BlogDocsLog inGet started
Tessl Logo

proxmox-service-guest-gate

Plan, inspect, approve, create, validate, and roll back a fresh Proxmox service guest while protecting legacy guests. Use before creating or changing an LXC or VM for self-hosted services, especially on resource-constrained Proxmox hosts.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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, gate-driven workflow with strong validation and rollback checkpoints and lean, assumption-respecting prose. The main weaknesses are the missing referenced template file and the lack of concrete executable commands.

Suggestions

Add the missing templates/guest-change-request.md file (or correct the reference path), since it is cited in both the 'Required confirmation record' and 'Bundled resources' sections but does not exist in the bundle.

Include a few concrete executable examples (e.g., pct create / qm create command shapes or API calls) for the creation and validation steps to lift actionability from specific-but-instructional to copy-paste ready.

Deduplicate the field lists between the step-3 proposal parameters and the confirmation-record table to tighten the content and reduce repetition.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence without explaining Proxmox/LXC/VM basics, but the proposal-parameter list and confirmation table repeat several of the same fields, leaving minor tightening possible.

4 / 5

Actionability

Concrete, specific instruction-only guidance (exact fields to record, exact gate contents, exact rollback conditions) with only minor gaps, though it stops short of copy-paste-ready pct/qm CLI commands or API calls.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints ('Stop at the confirmation gate', 'Validate before data') and a feedback loop ('If the guest fails validation, stop deployment'), plus a checklist-style confirmation-record table.

5 / 5

Progressive Disclosure

Body is a clear overview with well-signaled one-level-deep references, but templates/guest-change-request.md is referenced twice yet does not exist in the bundle, a minor organization/navigation 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 strong, specific description that clearly states a comprehensive set of actions and an explicit use-when trigger, with a distinct Proxmox-creation niche. Slightly less exhaustive on natural trigger synonyms, which keeps trigger-term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ('Plan, inspect, approve, create, validate, and roll back') on a clearly scoped object ('a fresh Proxmox service guest'), plus a protective constraint, giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (the six actions plus legacy-guest protection) and 'when' ('Use before creating or changing an LXC or VM for self-hosted services') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-keyword coverage ('creating or changing an LXC or VM', 'self-hosted services', 'resource-constrained Proxmox hosts') that a user would actually say, but missing common synonyms/variants such as 'Proxmox VE' or 'container'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Proxmox service-guest creation gate) with distinct triggers ('LXC or VM', 'self-hosted services', 'resource-constrained Proxmox hosts') and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pvnkmnk/AgenticSelfHostSkills
Reviewed

Table of Contents

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.