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

89%

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

Quality

Content

78%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 highly actionable and well-sequenced for operating the local k8s dev environment, but it is a long single-file document with no progressive disclosure into bundled reference files, and some prose could be trimmed.

Suggestions

Split the Optional Add-ons detail (Keycloak OIDC, SPIRE/SPIFFE, Vault, BackendTLSPolicy) into separate reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce inline length.

Tighten the multi-paragraph prose describing helm:k3s:create side effects into a concise bullet list, keeping only what Claude cannot derive from the command itself.

Add an explicit validation checkpoint before destructive teardown (e.g. confirm `helm:k3s:status` or warn about the orphaned kubeconfig context before running helm:k3s:delete) to close the workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	Mostly dense and operational with executable commands and tables rather than concept explanations, but several prose paragraphs (e.g. the helm:k3s:create behavior description) could be tightened; lands above the midpoint but not fully lean.	4 / 5
Actionability	Copy-paste-ready commands throughout (mise run helm:*, kubectl, helm, skaffold) with concrete env-var overrides, port mappings, and a cert-extraction block covering the common cases.	5 / 5
Workflow Clarity	Clear sequencing from prerequisites through startup, teardown, add-ons, lifecycle, and chart checks, with checkpoints like `openshell gateway list`, `helm:k3s:status`, and a lint rerun loop; minor validation gaps before destructive teardown steps keep it below 5.	4 / 5
Progressive Disclosure	Well-organized into sections with a Key Files table, but it is a 360+ line monolithic file with no references/, scripts/, or assets/ bundle and no one-level-deep references; add-on details (Keycloak, SPIRE, Vault, BackendTLSPolicy) that could live in separate files are inlined.	3 / 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.

The description is specific, trigger-rich, and clearly scoped to the OpenShell local k8s dev environment. It explicitly answers both what the skill does and when to use it, with no voice or over-claim issues.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Start up, tear down, and configure') plus concrete coverage areas (cluster lifecycle, add-ons, HA testing, port mappings) with named tooling (k3d, Skaffold, Helm), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Clearly states what the skill does and gives explicit trigger guidance via the 'Trigger keywords - ...' clause (an equivalent of 'Use when...'), satisfying both the what and the when at the top anchor.	5 / 5
Trigger Term Quality	Provides a long explicit trigger-keyword list spanning natural phrases and synonyms ('local k8s', 'k3d', 'skaffold', 'start cluster', 'stop cluster', 'tear down cluster', 'dev cluster', 'HA'), matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	Scoped to the OpenShell local Kubernetes dev environment with specific tooling and add-ons, giving it a clear niche with minimal overlap risk against generic k8s skills.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

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

Reviewed: 5 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.