Tessl • The management layer for AI agent skills

The content is a strong, action-dense migration playbook with an explicit, well-validated workflow for a destructive operation. Its main weaknesses are minor conciseness trim opportunities and some inlined detail that could live in referenced files.

Suggestions

De-duplicate the protected hcloud resource-type list (currently stated in Safety Rules, the Plan gate, and the post-plan stop condition) into a single canonical list referenced where needed.

Move the long inline v2-only-input rg regex and the Special Cases catalog into a referenced file (e.g. docs/v2-to-v3-migration.md) to tighten the body and improve progressive disclosure.

Replace /path/to/kube-hetzner/scripts/ placeholders with a concrete resolution step (e.g. 'set KUBE_HETZNER_ROOT to the checked-out module path') so commands are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes competence with no basic concept explanations, but the ~340 lines include minor trim opportunities such as the protected-resource type list repeated three times and an inline ~50-name rg regex.	4 / 5
Actionability	Real terraform/jq/tofu commands and concrete rename mappings (e.g. k3s_token -> cluster_token) are highly executable, with only minor gaps from /path/to/ placeholders and 'Determine:' question steps that are not commands.	4 / 5
Workflow Clarity	An 8-step numbered sequence has explicit validation (terraform validate, strict auditor, jq delete/replace gate), feedback loops for error recovery, stop conditions, and a report checklist for a destructive operation.	5 / 5
Progressive Disclosure	A 'Canonical References' section clearly signals nine one-level-deep files with descriptions and defers detail to MIGRATION.md and docs/selinux.md, but no bundle files are present to verify and the long inlined Special Cases section is a minor organization gap.	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.

The description is a concise, specific trigger for a narrow niche with an explicit 'Use when' clause and minimal conflict risk. It is held back from a top score by fusing what and when into a single clause and naming only one action.

Suggestions

Separate the what and when: state the action(s) first, then a distinct 'Use when ...' clause, e.g. 'Renames and rewrites kube-hetzner Terraform inputs for the v2.x to v3.x module upgrade. Use when migrating an existing kube-hetzner root from v2 to v3.'

Add one or two concrete action verbs beyond 'migrating' (e.g. 'rewrites', 'audits the v3 plan') to lift specificity and trigger-term coverage.

Include a synonym such as 'upgrade' so users who say 'upgrade kube-hetzner' match the trigger.

Dimension	Reasoning	Score
Specificity	Names the domain (kube-hetzner Terraform root) and one concrete action (migrate v2.x to v3.x), but lists only a single action rather than several, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	An explicit 'Use when' clause provides a concrete trigger and the what is clear, but what and when are fused into one short clause with a single trigger phrase rather than each being separately elaborated.	4 / 5
Trigger Term Quality	Natural terms a user would say are present ('migrating', 'kube-hetzner', 'Terraform root', 'module v2.x to v3.x') with good coverage, though synonyms like 'upgrade' are missing.	4 / 5
Distinctiveness Conflict Risk	A highly specific niche (kube-hetzner v2->v3 module migration) with distinct triggers and minimal overlap risk with other skills.	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
Revision: 17e4746

Reviewed: 1 month ago

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.

migrate-v2-to-v3

Table of Contents

Is this your skill?