CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kh-assistant

Use when users need help with kube-hetzner configuration, debugging, or questions - acts as an intelligent assistant with live repo access

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/kh-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 body is highly actionable with clear, validated workflows for risky operations, but it is an 800-line monolith with no skill bundle files and repeated template boilerplate that hurts both conciseness and progressive disclosure.

Suggestions

Move the stable reference material (Hetzner server-type and location tables, the Common Issues catalog, and the full Terraform config templates) into files under references/ and link to them one level deep, leaving SKILL.md as an overview plus the startup checklist and critical rules.

Factor the repeated module boilerplate (source/version/hcloud_token/ssh keys/network_region) into a single documented base snippet and show only the differing nodepool/feature blocks per template to cut repetition.

Keep only the two or three most-used templates (Minimal dev, Production HA) inline and point the rest (Tailscale, Cilium, ARM, Super-HA) to reference examples to reduce token load.

DimensionReasoningScore

Conciseness

The ~800-line body is dense, novel domain reference rather than basic-concept padding, but it carries noticeable repetition (eight near-identical Terraform module blocks, recurring ssh_public_key boilerplate) that could be tightened without losing clarity.

3 / 5

Actionability

It provides concrete, executable bash/gh/terraform commands and complete config templates covering common cases, but templates require placeholder substitution (<LATEST>, YOUR_IP/32, var.hcloud_token) before they are copy-paste ready.

4 / 5

Workflow Clarity

Workflows (create, debug, teardown, upgrade, migrate) are explicitly numbered with validation checkpoints on destructive ops — the upgrade path runs terraform validate, plan -out, and the protected hcloud no-destroy gate, and the teardown path reviews an orphan report — satisfying the destructive-operation validation requirement.

5 / 5

Progressive Disclosure

Section headers and tables give good structure and repo docs (docs/llms.md, MIGRATION.md) are clearly signaled, but the skill ships no bundle files and inlines ~800 lines (server-type tables, location tables, eight config templates, issue catalog) that belong in reference files.

3 / 5

Total

15

/

20

Passed

Description

66%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 has an explicit, well-targeted trigger clause tied to a distinctive niche, but its capability statement leans on vague phrasing ("intelligent assistant with live repo access") and omits common synonyms like terraform, hetzner, k3s, and hcloud.

Suggestions

Replace "acts as an intelligent assistant with live repo access" with concrete capabilities, e.g. "answers configuration, debugging, and upgrade questions using the live terraform-hcloud-kube-hetzner repo."

Add natural synonyms users say (terraform, Hetzner Cloud, k3s/RKE2, hcloud) so the description triggers on a wider range of phrasings.

Tighten "or questions" to a more specific trigger such as "or version/upgrade questions" to reduce generic wording.

DimensionReasoningScore

Specificity

It names the domain and a couple of concrete activities ("kube-hetzner configuration, debugging, or questions"), but "questions" is generic and "acts as an intelligent assistant with live repo access" is vague fluff rather than a specific capability.

3 / 5

Completeness

It answers both halves — an explicit "Use when..." trigger clause and a (vague) "what" in "acts as an intelligent assistant with live repo access" — but the what is not concrete enough to reach a 5.

4 / 5

Trigger Term Quality

"kube-hetzner" plus "configuration"/"debugging" are natural terms a user would say, but common synonyms and variations a user might also use (terraform, hetzner cloud, k3s, RKE2, hcloud) are absent.

3 / 5

Distinctiveness Conflict Risk

"kube-hetzner" is a highly specific product niche with distinct triggers, so overlap with other skills is minimal.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (809 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

mysticaltech/terraform-hcloud-kube-hetzner

Path

.claude/skills/kh-assistant/SKILL.md

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.