CtrlK
BlogDocsLog inGet started
Tessl Logo

helm-chart-builder

Helm chart development agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw — chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing. Use when: user wants to create or improve Helm charts, design values.yaml files, implement template helpers, audit chart security (RBAC, network policies, pod security), manage subcharts, or run helm lint/test.

67

Quality

81%

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

The canonical home for this skill is helm-chart-builder in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 dense, well-organized reference with copy-paste template patterns and concrete checklists, but it is monolithic and references script bundle files that are absent from the package. Adding feedback loops to the audit workflows and providing the referenced scripts would lift the weaker dimensions.

Suggestions

Ship the referenced scripts (scripts/chart_analyzer.py, scripts/values_validator.py, scripts/convert.sh) or remove the commands that invoke them so the documented tooling actually exists.

Add explicit validate-fix-retry feedback loops to the /helm:review and /helm:security workflows, mirroring the validate step already present in /helm:create.

Move the large Template Patterns and Dependency Management reference blocks into separate reference files (e.g., references/templates.md, references/dependencies.md) and link to them from SKILL.md to reduce monolithic length and improve navigation.

DimensionReasoningScore

Conciseness

Mostly efficient dense reference material (severity/fix tables, ASCII trees, copy-paste templates) that assumes Helm/Kubernetes knowledge rather than explaining basics, though at ~440 lines some sections like the values-design and dependency ASCII blocks could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready template patterns, a security-hardened pod spec, and concrete helm commands, but several commands depend on scripts/chart_analyzer.py, scripts/values_validator.py, and scripts/convert.sh that are not present in the bundle.

4 / 5

Workflow Clarity

The /helm:create, /helm:review, and /helm:security workflows are clearly numbered with a validate checkpoint (helm lint/template) in scaffolding, but the review and security audit workflows lack explicit validate-fix-retry feedback loops.

4 / 5

Progressive Disclosure

Sections are clearly headed and organized, but the body is a monolithic ~440-line file with template patterns and audit checklists inlined rather than split into referenced files, and it cites scripts/ files (chart_analyzer.py, values_validator.py, convert.sh) that do not exist in the bundle.

3 / 5

Total

15

/

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 description that clearly states what the skill does and when to use it, with concrete actions and natural trigger terms in third-person voice. Only minor gap is the absence of some file-extension synonyms among trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ("chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing") and when ("Use when: user wants to create or improve Helm charts, design values.yaml files...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords ("Helm charts", "values.yaml", "subcharts", "helm lint/test", "RBAC", "network policies", "pod security") but lacks some synonyms and file-extension variants such as Chart.yaml, .yaml, or _helpers.tpl.

4 / 5

Distinctiveness Conflict Risk

Clear Helm-specific niche with distinct triggers (values.yaml, subcharts, helm lint/test) that are unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

19

/

20

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: 10 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.