upgrade-cluster

Use when upgrading or hardening an existing kube-hetzner cluster, including module version bumps, provider lockfile refreshes, k3s/RKE2 channel/version upgrades, immutable node replacement, system-upgrade-controller changes, or live cluster rollout validation

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

88%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 dense, highly actionable runbook with excellent workflow sequencing and validation feedback loops for risky live-cluster operations. Its main weaknesses are minor: version-sensitive statements sit inline rather than in a deprecated section, and several referenced bundle paths (scripts/, docs/) are missing while Phase 3 duplicates content already in the reference file.

Suggestions

Move version-sensitive claims (kube-hetzner v2.20 eth1 naming, RKE2 4GB cx23 floor) into a dedicated 'Version notes / deprecated patterns' section so they can be updated without cluttering the main workflow.

Create the referenced scripts/destroy.sh, scripts/cleanup.sh, and docs/selinux.md (or remove the references) so all cited paths resolve.

Trim the inlined Phase 3 subsections (Capacity, Stateful Workloads, Worker/Control-Plane Replacement) to a concise summary and defer detail to references/immutable-node-replacement.md to avoid duplication.

Dimension	Reasoning	Score
Conciseness	The 380-line body is mostly lean, actionable bash with tight domain-specific prose, but includes inline version-sensitive assertions ('Kube-hetzner v2.20 expects the private network interface to be named eth1', 'RKE2 no longer implies an 8GB control-plane floor') that are not segregated into a deprecated/old-patterns section, a minor conciseness penalty.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (terraform init/plan/apply flags, kubectl queries, the jq no-destroy gate pipeline, hcloud and ssh commands) with appropriate placeholders, covering the common upgrade cases concretely.	5 / 5
Workflow Clarity	Clear multi-phase sequence (Preflight, Phase 1 Module Convergence, Phase 2 Runtime Upgrade, Phase 3 Immutable Replacement, Firewall Closure, Final Report) with explicit validation checkpoints, stop conditions ('Any output is a stop condition'), feedback loops (validate -> repair -> re-prove), and a Final Report checklist, appropriate for destructive/batch live-cluster operations.	5 / 5
Progressive Disclosure	Good section structure with a well-signaled one-level-deep reference ('For the full field-proven workflow, read references/immutable-node-replacement.md'), but the body references scripts/destroy.sh, scripts/cleanup.sh, and docs/selinux.md that do not exist, and Phase 3 inlines substantial detail that overlaps the existing reference file.	4 / 5
	Total	18 / 20 Passed

Description

83%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 names concrete actions and an explicit 'Use when' trigger for a well-scoped niche. It falls just short of top marks on trigger-term quality and completeness because the when-clause is combined with the what rather than framed as distinct user-mention triggers, and some terms are jargon-leaning.

Dimension	Reasoning	Score
Specificity	Lists six concrete upgrade/hardening actions ('module version bumps, provider lockfile refreshes, k3s/RKE2 channel/version upgrades, immutable node replacement, system-upgrade-controller changes, or live cluster rollout validation'), giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both what (the enumerated upgrade/hardening actions) and when ('Use when upgrading or hardening an existing kube-hetzner cluster'), but the trigger is a single combined clause rather than separate explicit user-mention trigger phrases.	4 / 5
Trigger Term Quality	Good natural keyword coverage for the niche ('upgrading', 'hardening', 'kube-hetzner cluster', 'k3s/RKE2', 'module version bumps'), but leans technical with phrases like 'provider lockfile refreshes' and 'system-upgrade-controller changes' and omits common synonyms like 'patch' or 'update'.	4 / 5
Distinctiveness Conflict Risk	Targets a tightly scoped niche (kube-hetzner cluster upgrades) with distinct, domain-specific triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: mysticaltech/terraform-hcloud-kube-hetzner
Path: .claude/skills/upgrade-cluster/SKILL.md
Commit: bb1622c

Reviewed: 1 day 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.