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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 thorough, actionable skill body with executable code, well-structured workflows, and validation checkpoints backed by real bundle scripts. Its main weakness is conciseness — it restates some familiar Helm/Kubernetes conventions — and references that are present on disk but not all clearly signaled from the body.

Suggestions

Trim restatements of well-known Kubernetes/Helm conventions (e.g., explanations of standard app.kubernetes.io labels and probe semantics) to assume Claude's competence and reduce token load.

Make the existing references explicit in the body: link references/chart-patterns.md and references/values-design.md from the Template Patterns and Values Design sections, and move the bulk of the inlined template patterns into those reference files to keep SKILL.md an overview.

Add an explicit error-recovery feedback loop to the /helm:review and /helm:security workflows (e.g., 'fix findings -> re-run chart_analyzer.py -> only clear when zero CRITICAL/HIGH') to elevate workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient tables and tree diagrams, but several sections restate widely-known Helm/Kubernetes conventions (standard label keys, probe semantics) and the slash-command tables duplicate information Claude already knows, adding padding that could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready code (helper templates, conditional resources, hardened pod spec) and concrete executable commands (chart_analyzer.py, values_validator.py, helm lint/template) covering the common chart-building cases.

5 / 5

Workflow Clarity

Each slash command has a clear numbered sequence with an explicit validation step (chart_analyzer.py + helm lint + helm template), but error-recovery feedback loops are implicit rather than spelled out, and the review/security workflows end at report generation without re-validation.

4 / 5

Progressive Disclosure

Body is well-organized with clear sections and concrete script references (scripts/chart_analyzer.py, scripts/values_validator.py) that resolve to real bundle files, plus references/chart-patterns.md and references/values-design.md exist; however the body inlines substantial template-pattern and values-design content that overlaps those reference files rather than purely pointing to them, and references are not all linked from the body.

4 / 5

Total

16

/

20

Passed

Description

100%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: it states comprehensive concrete capabilities and pairs them with an explicit, keyword-rich 'Use when' trigger clause. It is concise despite the breadth, third-person, and clearly distinguishable from related DevOps skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing' — covering the full chart lifecycle comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated capabilities) and 'when' via the concrete 'Use when:' clause with several trigger phrases, matching the 5-anchor example closely.

5 / 5

Trigger Term Quality

Comprehensive natural keyword coverage including synonyms and file/CLI specifics: 'Helm charts', 'values.yaml', 'template helpers', 'subcharts', 'RBAC', 'network policies', 'pod security', 'helm lint/test'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Helm chart construction/security) with distinct Kubernetes-native triggers unlikely to fire for adjacent skills like docker-development or senior-devops.

5 / 5

Total

20

/

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.

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.