migrate-v2-to-v3

Use when migrating an existing kube-hetzner Terraform root from module v2.x to v3.x

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/migrate-v2-to-v3/SKILL.md

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 high-quality, deeply actionable migration runbook with strong workflow guardrails for a destructive operation. Its only real weakness is repetition that bloats token cost and slight over-inlining of reference-grade material.

Suggestions

Consolidate the protected hcloud resource-type list (currently repeated in Safety Rules, the jq gate, and the post-rename check) and the k3s_channel default-change explanation (currently in both Safety Rules and Workflow step 4) into a single canonical mention referenced where needed.

Move the long v2-only-inputs regex and the 'Interpret Special Cases' catalog into a bundle reference file so SKILL.md stays a lean operational overlay.

Render the Canonical References as markdown links where the files live alongside the skill, to make navigation one click rather than a path lookup.

Dimension	Reasoning	Score
Conciseness	The body is information-dense with no beginner-concept padding, but it repeats the protected hcloud resource-type list three times and re-explains the k3s_channel default change twice, which is more than the 'minor' trimming of anchor 4.	3 / 5
Actionability	Fully executable, copy-paste-ready bash (state pull, fmt, init, validate, plan, jq gates), exact variable rename mappings, and script invocations with concrete flags cover the common migration cases comprehensively.	5 / 5
Workflow Clarity	An 8-step sequence with explicit validation checkpoints (back up → terraform validate → no-destroy jq gate → explicit apply approval), feedback loops on validation failure, and a report checklist; the destructive operation is well-guarded so no 3-cap applies.	5 / 5
Progressive Disclosure	Clear sections and well-signaled one-level-deep repo references (Canonical References each get a one-line description), but references are plain backtick paths rather than navigable links and some dense inline content (the long v2-only regex, the special-cases catalog) could be externalized, keeping it below anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

73%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 tight, distinctive trigger that explicitly answers both what and when for a well-bounded niche. It is held back from the top band only by a single generic action verb and the absence of synonyms like 'upgrade'.

Suggestions

Enumerate 1-2 concrete sub-actions in the description (e.g., 'renames v2 variables, inverts disable_ booleans, and gates destructive plan changes') to lift specificity beyond the single 'migrating' verb.

Add a synonym trigger such as 'upgrade' alongside 'migrating' so users who ask to 'upgrade kube-hetzner to v3' also activate the skill.

Dimension	Reasoning	Score
Specificity	The description names a hyper-specific domain ('kube-hetzner Terraform root', 'module v2.x to v3.x') but only a single concrete action verb ('migrating'), matching anchor 3's '1-2 concrete actions, but not comprehensive' rather than the several actions required for a 4.	3 / 5
Completeness	It has both a 'what' (migrate kube-hetzner root v2 to v3) and an explicit 'Use when…' trigger, so it clears the 3-cap for missing trigger guidance, but the single fused action/trigger lacks the multi-phrase breadth of anchor 5.	4 / 5
Trigger Term Quality	Natural terms a user would actually say are present ('migrating', 'kube-hetzner', 'Terraform', 'v2.x to v3.x'), giving good coverage; it stops short of anchor 5 only because synonyms like 'upgrade' are missing.	4 / 5
Distinctiveness Conflict Risk	The trigger carves an extremely narrow niche (kube-hetzner module v2.x→v3.x migration) with distinct, specific terms and minimal realistic overlap with any other skill.	5 / 5
	Total	16 / 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: 5 missing	Warning

	Total	15 / 16 Passed

Repository: mysticaltech/terraform-hcloud-kube-hetzner
Path: .claude/skills/migrate-v2-to-v3/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.