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

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

40%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 skill body is a thin, generic shell that explains what a Helm chart skill should do in the abstract without any executable Helm guidance, and its sole reference points to a non-existent path. The actual bundle assets (chart-structure.md, validate-chart.sh, templates) are not surfaced.

Suggestions

Replace the generic 'Instructions' with concrete Helm steps, e.g. `helm create <name>`, editing Chart.yaml/values.yaml, `helm lint`, `helm template`, and `helm package`, mirroring the structure in references/chart-structure.md.

Fix the broken reference: point to the real file `references/chart-structure.md` (and `scripts/validate-chart.sh`) instead of the non-existent `resources/implementation-playbook.md`.

Add a validation checkpoint (e.g. run `scripts/validate-chart.sh` or `helm lint`/`helm template --debug`) before packaging, since chart packaging/deployment is a batch-style operation that warrants verification.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly free of padding, but the generic instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') are boilerplate that adds little Helm-specific value.	4 / 5
Actionability	No concrete Helm commands, template snippets, or examples appear in the body—only abstract directives like 'Provide actionable steps and verification'; the actual executable guidance is entirely deferred to a referenced file.	2 / 5
Workflow Clarity	The 'Instructions' list is a vague four-item sequence with no Helm-specific ordering and no explicit validation checkpoints, despite this skill involving packaging/deploy operations that benefit from verification.	2 / 5
Progressive Disclosure	The body references 'resources/implementation-playbook.md' (twice) but that file does not exist; the real bundle file is 'references/chart-structure.md', which is never mentioned, so navigation is broken and the reference is mis-signed.	2 / 5
	Total	10 / 20 Passed

Description

83%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.

The description is well-crafted: third person, clear 'Use when' trigger, concrete domain and actions. It explicitly covers what and when with minimal fluff.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several specific actions ('Design, organize, and manage Helm charts', 'templating and packaging Kubernetes applications'), though the verbs stay somewhat generic relative to a 5-anchor that enumerates concrete distinct operations.	4 / 5
Completeness	Explicitly answers both 'what' (design/organize/manage Helm charts for templating and packaging) and 'when' (a clear 'Use when' clause with concrete trigger phrases).	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('creating Helm charts', 'packaging Kubernetes applications', 'implementing templated deployments') but lacks synonyms or the file extension cue (e.g., 'Chart.yaml', '.tgz').	4 / 5
Distinctiveness Conflict Risk	The Helm/Kubernetes packaging niche is fairly distinct with specific triggers, but the broad 'templated deployments' phrasing could mildly overlap with general K8s or IaC skills.	4 / 5
	Total	17 / 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: rmyndharis/antigravity-skills
Path: skills/helm-chart-scaffolding/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.