CtrlK
BlogDocsLog inGet started
Tessl Logo

homelab-change-planner

Plans homelab infrastructure changes with pre-flight checks, rollback strategies, and impact analysis before any execution.

60

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/homelab-change-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The content is well-structured, lean, and actionable with a clear sequenced workflow and a concrete template. The main gap is an explicit feedback loop tying a failed post-check to the rollback plan, which currently stays implicit.

Suggestions

Add an explicit error-recovery step, e.g. 'If post-check fails, execute the rollback plan from step 5, then re-run the post-check.'

Provide concrete criteria for the LOW/MEDIUM/HIGH risk rating (e.g. reversibility + blast radius thresholds) so step 4 is unambiguous.

Drop the redundant restatement of the description in the opening paragraph to tighten conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the opening paragraph restates the frontmatter description, a minor redundancy that could be trimmed.

4 / 5

Actionability

A concrete 9-step workflow plus a copy-paste Change Plan Template give mostly executable guidance, though a few steps (risk-rating criteria, dependency identification) remain high-level.

4 / 5

Workflow Clarity

Steps are clearly sequenced with real checkpoints (state snapshot, approval gate, per-step confirmation, post-check), but the explicit error-recovery loop linking a failed post-check to the prepared rollback is only implicit.

4 / 5

Progressive Disclosure

A short, well-organized skill under 50 lines with clear section headers and one-level external references (companion skills, a Proxmox doc URL), needing no bundle files.

5 / 5

Total

17

/

20

Passed

Description

58%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.

The description clearly conveys what the skill does and names a distinct niche, but it lacks an explicit 'Use when...' trigger and natural trigger-term coverage, capping completeness and trigger quality. Adding concrete invocation triggers would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases (e.g., 'Use when modifying homelab servers, containers, or network config, or before applying any infrastructure change').

Broaden trigger-term coverage with synonyms users actually say (e.g., 'update', 'reconfigure', 'before changing my server/container').

Tighten the action list from categories to specific concrete actions (e.g., 'snapshots state, rates risk LOW/MEDIUM/HIGH, drafts rollback steps') to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the homelab domain and lists several concrete actions ('pre-flight checks, rollback strategies, and impact analysis'), though they remain fairly high-level categories rather than a comprehensive action set.

4 / 5

Completeness

The 'what' is clear, but 'when' is only weakly implied by 'before any execution' rather than an explicit 'Use when...' trigger, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'homelab infrastructure changes' is a relevant natural term, but common user phrasings and synonyms (modifying servers, updating containers, before changing the homelab) are missing and there is no explicit trigger clause.

3 / 5

Distinctiveness Conflict Risk

The homelab change-planning niche is clear and distinct, but closely related companion skills (homelab-safe-ops, homelab-topology-mapper) create minor overlap risk.

4 / 5

Total

14

/

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.