helm-dev-environment

Start up, tear down, and configure the local Kubernetes development environment for OpenShell. Uses k3d (Docker-backed k3s) + Skaffold + Helm. Covers cluster lifecycle, optional add-ons (Keycloak OIDC, Envoy Gateway), HA testing, and port mappings. Trigger keywords - local k8s, local cluster, k3d, skaffold, helm dev, start cluster, stop cluster, tear down cluster, delete cluster, create cluster, helm:k3s, helm:skaffold, local dev environment, dev cluster, k8s dev, envoy gateway local, keycloak local, high availability, HA.

Quality

82%

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

Quality

Content

65%Weight 40%Scale 1-3

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 highly actionable, command-rich runbook for a complex stack, but it is long and monolithic with no progressive disclosure to reference files, and destructive teardown lacks an explicit validation gate. Tightening prose and gating the delete step would raise it.

Suggestions

Add an explicit pre-check before destructive teardown (e.g., confirm releases/context, or a 'helm:k3s:status' gate) so delete operations have a validation checkpoint.

Trim explanatory prose around sidecar policy modes and the SPIRE trust-domain/auth path to the minimum needed to run the commands, improving token efficiency.

Split the Optional Add-ons (Keycloak, Envoy Gateway, SPIRE) and the mTLS cert-extraction detail into reference files linked from the main body, giving the SKILL.md a leaner overview with one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content that avoids explaining basics, but several prose passages (sidecar policy/SYS_PTRACE detail, SPIRE trust-domain explanation) could be tightened, fitting 'mostly efficient but could be tightened'.	2 / 3
Actionability	Fully executable, copy-paste-ready commands throughout ('mise run helm:k3s:create', 'kubectl port-forward', base64 cert-extraction blocks), matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced and the Helm lint section has a validate-fix-retry loop, but destructive teardown ('helm:k3s:delete') lacks an explicit pre-validation checkpoint, capping the score at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Well-organized into sections with a Key Files index table, but it is a single monolithic file over 50 lines with no separate reference files; detailed add-on and mTLS content that could be split remains inline.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, third-person, and richly triggers: it states concrete capabilities and supplies an explicit keyword list for when to invoke the skill. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Start up, tear down, and configure', 'cluster lifecycle', 'HA testing', 'port mappings') plus named add-ons (Keycloak OIDC, Envoy Gateway), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what the skill does and provides explicit trigger guidance via the 'Trigger keywords - ...' clause, which counts as equivalent explicit trigger guidance and avoids the cap at 2.	3 / 3
Trigger Term Quality	An explicit 'Trigger keywords' list gives broad natural coverage users would say ('local k8s', 'k3d', 'skaffold', 'start cluster', 'tear down cluster', 'HA'), matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to the OpenShell local Kubernetes dev environment with k3d+Skaffold+Helm and distinct triggers, making it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: NVIDIA/OpenShell
Path: .agents/skills/helm-dev-environment/SKILL.md
Commit: deced87

Reviewed: 6 days 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.