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 kics-policy.

73

Quality

92%

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

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, highly actionable, and clearly sequenced, with executable commands and concrete YAML examples throughout. Its weaknesses are implicit validation checkpoints in the riskier flows and a monolithic single-file structure with no bundle files for progressive disclosure.

Suggestions

Add explicit validation checkpoints to the riskier workflows, e.g. after Step 7's git-stash diff and in Step 8's CI job, state 'only proceed/merge when helm lint AND helm unittest pass' as a feedback loop.

Split the inline assertion catalog (Step 3 table) and the test-authoring example into a references/ file (e.g. references/assertions.md) and link to it from SKILL.md to enable one-level-deep progressive disclosure.

Add a brief verification note in Step 2 or Step 4 confirming how to check that a test actually ran and passed (e.g. expected exit code / pass-fail summary) so the workflow has a clear success signal.

DimensionReasoningScore

Conciseness

The body is lean and step-organized with executable commands and tight tables; it assumes Claude's competence and avoids explaining concepts Claude already knows.

3 / 3

Actionability

Provides fully executable helm/unittest commands, complete copy-paste YAML test examples with set/asserts, and a CI workflow, all specific and ready to run.

3 / 3

Workflow Clarity

Steps 1-9 are clearly sequenced, but validation checkpoints are mostly implicit (only 'helm plugin list # verify'); the git-stash diff flow and CI run lack explicit validate-then-proceed feedback loops, so workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

No bundle files exist and all content lives inline in a ~210-line SKILL.md; sections are well-organized but content that could be split (assertion catalog, test-authoring guide) is inline, matching the score-2 anchor rather than a clean one-level-deep split.

2 / 3

Total

10

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete with explicit what-and-when guidance, while clearly distinguishing itself from sibling policy/scanning skills. It is a strong, copy-ready description with no vague padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (installs the plugin, authors tests/*.yaml, asserts via isKind/equal/matchRegex/snapshots, plus helm lint and helm template), matching the highest anchor.

3 / 3

Completeness

Explicitly answers both what (installs/authors/asserts/lint/template) and when ('Use to verify a chart's template logic and rendered shape'), matching the what-and-when anchor.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('Helm chart unit testing', 'helm lint', 'helm template', 'rendered shape') with good coverage rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

Explicitly carves a niche ('unit-level correctness testing, not security scanning') and redirects policy/scanning to named peer skills, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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