helm-chart-scaffolding

Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/kubernetes-operations/skills/helm-chart-scaffolding/SKILL.md

Quality

Content

57%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 a clean, concise overview hub, but it offloads the actionable workflow and leaves several real bundle files orphaned with no navigation. Adding a short sequenced workflow with a validation checkpoint and links to the existing scripts/templates would materially raise actionability and workflow clarity.

Suggestions

Add a brief step-by-step scaffolding workflow in the body (helm create -> edit values/templates -> helm dependency update -> helm lint/template -> package) with an explicit validation checkpoint before packaging.

Link the existing bundle files from the body, e.g. point to scripts/validate-chart.sh for validation and assets/Chart.yaml.template and assets/values.yaml.template for starting points, plus references/chart-structure.md for layout.

Remove or merge the redundant Purpose and When-to-Use sections with the frontmatter description to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, using short lists and commands without explaining what Helm or Kubernetes are, but the Purpose and When-to-Use sections partly restate the frontmatter description and could be trimmed.	4 / 5
Actionability	The Troubleshooting section gives executable commands (helm template --debug, helm dependency update, helm install --dry-run), but the core scaffolding how-to is delegated to references/details.md and the Best Practices are directives rather than runnable steps.	3 / 5
Workflow Clarity	There is no sequenced build/package workflow with validation checkpoints in the body itself; 'Validate charts before packaging' is only a best-practice bullet, and packaging is a batch operation that the rubric caps at 3 without explicit validation steps.	3 / 5
Progressive Disclosure	The body signals one reference (references/details.md) clearly one level deep, but the other bundle files (references/chart-structure.md, scripts/validate-chart.sh, assets/Chart.yaml.template, assets/values.yaml.template) are never linked or navigated from the body, leaving real content poorly signaled.	3 / 5
	Total	13 / 20 Passed

Description

87%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, well-structured description that clearly states capability and explicit usage triggers in third-person voice. Minor gains are available by adding more granular action verbs and a few synonymous trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain (Helm charts, Kubernetes) and several concrete actions ('Design, organize, and manage', 'templating and packaging', 'reusable configurations'), but the verbs stay somewhat high-level without enumerating specific tasks like linting, repository setup, or rollback.	4 / 5
Completeness	It explicitly answers both 'what' (Design, organize, and manage Helm charts for templating and packaging Kubernetes applications) and 'when' (Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('creating Helm charts', 'packaging Kubernetes applications', 'templated deployments') that users would actually say, though common synonyms/extensions like 'K8s', 'Helm release', or '.yaml chart' are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche around Helm chart scaffolding with distinct triggers, and is unlikely to fire for unrelated Kubernetes or general packaging skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/kubernetes-operations/skills/helm-chart-scaffolding/SKILL.md
Commit: d6837ae

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.