CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-v2-to-v3

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

76

Quality

95%

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

100%Weight 40%Scale 1-3

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 migration playbook with a clear sequenced workflow, explicit validation gates and stop conditions, and well-organized sections. It is long but not padded — the length reflects real migration complexity rather than wasted tokens.

DimensionReasoningScore

Conciseness

The body is information-dense operational guidance — variable rename maps, jq safety gates, and copy-paste bash — with no padding explaining concepts Claude already knows; every section earns its tokens despite the length being driven by genuine migration complexity.

3 / 3

Actionability

It provides fully executable commands (terraform version/init/validate/plan, tofu validate, rsync), concrete jq destructive-action gates, and exact variable-to-variable rename mappings that are copy-paste ready.

3 / 3

Workflow Clarity

An explicit 8-step sequence (Inspect → Back Up → Rewrite → Decide Intent → Init/Validate → Plan → Special Cases → Report) with validation checkpoints (terraform validate, plan gate) and feedback loops (re-read variables.tf on validation failure, stop-and-diagnose on protected deletes).

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), so per the simple-skill scoring note a single well-organized file qualifies; sections are clearly delineated and the canonical-references list is explicitly signaled one level deep.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 concise, well-targeted description with an explicit "Use when" trigger, strong natural keyword coverage, and a distinctive niche. Its only weakness is that it describes a single action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

The phrase "migrating an existing kube-hetzner Terraform root from module v2.x to v3.x" names a concrete domain and a single specific action, but unlike the score-3 anchor it does not list multiple distinct concrete actions (e.g. extract, fill, merge).

2 / 3

Completeness

It explicitly answers both what (migrate a kube-hetzner Terraform root v2.x to v3.x) and when via the explicit "Use when migrating..." trigger, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user phrasing is well represented — "migrating", "kube-hetzner", "Terraform root", "module v2.x to v3.x" are exactly the terms an operator would say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The trigger is narrowly scoped to kube-hetzner module v2.x-to-v3.x migration, a clear niche unlikely to fire for any other skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

15

/

16

Passed

Repository
mysticaltech/terraform-hcloud-kube-hetzner
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.