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

57%

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

15%

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

The body is well-sectioned but largely hollow: instructions are generic and non-executable, there is no sequenced workflow with validation, and the single resource reference points to a nonexistent `resources/` path while the real bundle files go unlinked. This makes the skill unactionable as written.

Suggestions

Replace the abstract Instructions with concrete, executable steps (e.g. `helm create <chart>`, editing Chart.yaml/values.yaml templates, `helm lint`, `helm template`) and reference the actual `assets/*.template` and `scripts/validate-chart.sh` files.

Fix the broken reference: point to the real bundle files (`references/chart-structure.md`, `scripts/validate-chart.sh`) instead of the nonexistent `resources/implementation-playbook.md`.

Add a sequenced workflow with explicit validation checkpoints (run `validate-chart.sh` / `helm lint`, fix errors, re-validate) before packaging, capping workflow clarity above its current level.

Dimension	Reasoning	Score
Conciseness	The body is mostly terse and assumes Claude's competence, but the "Do not use this skill when" section ("The task is unrelated to helm chart scaffolding" / "You need a different domain or tool outside this scope") is generic boilerplate that applies to any skill and the opening line repeats the frontmatter description, so it could be tightened.	2 / 3
Actionability	The Instructions ("Clarify goals", "Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") are abstract with no concrete commands like `helm create`, no code, and no executable examples — it describes rather than instructs.	1 / 3
Workflow Clarity	There is no sequenced multi-step workflow and no validation checkpoints despite packaging/chart generation being a batch-style operation; the instructions are unordered abstract bullets.	1 / 3
Progressive Disclosure	The body's only reference is `resources/implementation-playbook.md`, which does not exist, while the actual bundle files (`references/chart-structure.md`, `scripts/validate-chart.sh`, `assets/Chart.yaml.template`, `assets/values.yaml.template`) are never mentioned — navigation to the detailed materials is broken.	1 / 3
	Total	5 / 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 strong: it states concrete capabilities, includes natural user-facing trigger terms, and gives an explicit "Use when" clause covering both what and when. It is a clear, distinct niche unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Design, organize, and manage Helm charts", "templating and packaging", "creating", "packaging", "implementing templated deployments" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers what ("Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations") and when ("Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments"), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural terms a user would say ("creating Helm charts", "packaging Kubernetes applications", "templated deployments") are well covered; not jargon-heavy and matches the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	"Helm charts" + "Kubernetes applications" + "templated deployments" carve a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: e63f7dd

Reviewed: about 23 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.