CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/helm-chart-tester

Configures helm-unittest for Helm chart unit testing - installs the `helm-unittest` plugin, authors `tests/*.yaml` per template, asserts on rendered manifests (`isKind`, `equal`, `matchRegex`, snapshots), plus `helm lint` and `helm template` render testing. Use to verify a chart's template logic and rendered shape; this is unit-level correctness testing, not security scanning - to enforce policy on rendered manifests use policy-as-code-runner, and to scan charts for misconfigurations use checkov-policy or trivy-config.

72

Quality

90%

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

Overview
Quality
Evals
Security
Files

Quality

Content

82%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 well-structured, highly actionable skill body with executable examples at every step and useful Anti-patterns/Limitations sections. Minor gains available from tightening a few asides and making test-failure recovery explicit inline.

Suggestions

Add an inline 'if a test fails' recovery note in Step 4 (re-read the assertion, fix the template or the test, re-run) to turn the implicit loop into an explicit checkpoint.

Trim conversational asides like 'Useful for review: "what does this change actually produce?"' in Step 7 to keep the body token-lean.

Consider splitting the large assertion table (Step 3) or the CI snippet into a referenced file if the skill grows, to keep SKILL.md as a pure overview.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Helm knowledge (no 'what is a chart' padding), with only minor trimmable asides like 'Useful for review: "what does this change actually produce?"'.

4 / 5

Actionability

Fully executable throughout — install commands, a complete test YAML, an assertion reference table, run commands, CI config, and conftest piping — copy-paste ready and covering common cases.

5 / 5

Workflow Clarity

Steps 1–9 are clearly sequenced with a verify step ('helm plugin list # verify') and lint as a checkpoint, though explicit test-failure recovery loops are only implicit via the Anti-patterns section rather than inline.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and a clearly signaled one-level-deep References section; no bundle files exist, and the moderate length is appropriately contained in one navigable file.

4 / 5

Total

17

/

20

Passed

Description

92%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, an explicit use-trigger, and clear boundaries against sibling skills. Trigger-term coverage is the only minor gap, lacking a few natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'installs the helm-unittest plugin, authors tests/*.yaml per template, asserts on rendered manifests (isKind, equal, matchRegex, snapshots), plus helm lint and helm template render testing' — covering the full workflow comprehensively.

5 / 5

Completeness

Explicitly answers both what ('Configures helm-unittest...installs, authors, asserts, lint, template') and when ('Use to verify a chart's template logic and rendered shape') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Helm chart unit testing', 'helm lint', 'helm template', 'rendered manifests') that users would say, though a few common phrasings like 'test my chart' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Helm chart unit testing) with explicit boundary guidance distinguishing it from policy-as-code-runner, checkov-policy, and trivy-config, minimizing wrong-skill triggers.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents