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

80%

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 ./.agents/skills/helm-dev-environment/SKILL.md

Quality

Content

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

A highly actionable, well-structured operational runbook with concrete commands throughout. It loses points on conciseness (redundant forwarding detail and overall length), workflow clarity (no validation on destructive teardown), and progressive disclosure (monolithic single file rather than an overview pointing to references).

Suggestions

De-duplicate the port-forwarding details (OTLP 4317, trace UI 18888, gateway 8090) — describe them once and cross-reference, trimming the redundant Deploy/Viewing sections.

Add a verification checkpoint to destructive teardown (e.g., run `mise run helm:k3s:status` after `helm:k3s:delete` and confirm no cluster remains) so the workflow clears the destructive-operation cap.

Move the Optional Add-ons procedures (Envoy, Keycloak, SPIRE) and the mTLS cert-extraction block into one-level-deep reference files under references/, keeping SKILL.md a concise overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic-concept padding (no explaining what k8s/Helm is), but the doc is long (~326 lines) and repeats port-forwarding details (OTLP 4317, trace UI 18888, gateway 8090) across the Deploy and Viewing local traces sections. Not a 4 because the redundancy and length are more than minor.	3 / 5
Actionability	Dense with copy-paste-ready mise/helm/kubectl commands, env-var tables with defaults, a TLS-behavior table, and a complete mTLS cert-extraction block; the common cases (create, dev/run/sidecar, forward, teardown, stop/start, lint, add-ons) are all covered with executable commands.	5 / 5
Workflow Clarity	Sequencing is clear (Prerequisites → Startup → Teardown → Add-ons → Lifecycle → Checks) and the Helm lint section has a validate-fix-retry loop, but destructive teardown (helm:k3s:delete, helm:skaffold:delete) lacks any validation/verification checkpoint, invoking the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	A well-sectioned single-file runbook with a useful Key Files navigation table, but ~326 lines of inline procedures (Envoy/Keycloak/SPIRE add-ons, mTLS cert extraction, HA) that could be split into one-level reference files; no bundle files are provided, so there is no file-based disclosure at all.	3 / 5
	Total	14 / 20 Passed

Description

95%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 strong: concrete actions, a comprehensive natural-language trigger-keyword list, and a clearly defined, low-conflict niche. The only minor weakness is that the 'when' guidance is delivered as a keyword dump rather than a natural 'Use when...' sentence.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Start up, tear down, and configure') plus named tools (k3d, Skaffold, Helm) and coverage areas (cluster lifecycle, add-ons, HA testing, port mappings); comprehensive scope, though the core action verbs are limited to three. Not a 5 because the distinct action list is narrower than the multi-action anchor example.	4 / 5
Completeness	Clearly states what the skill does ('Start up, tear down, and configure the local Kubernetes development environment for OpenShell') and provides explicit 'when' guidance via a dedicated concrete trigger-keyword list, satisfying the 'equivalent explicit trigger guidance' exception to the Use-when cap.	5 / 5
Trigger Term Quality	An extensive explicit 'Trigger keywords' list with natural phrases and synonyms a user would actually say (local k8s, k3d, skaffold, start/stop/tear down/delete/create cluster, HA/high availability). Matches the comprehensive-synonyms anchor; no natural term category is missing for this domain.	5 / 5
Distinctiveness Conflict Risk	A highly specific niche (OpenShell local k8s dev via k3d/Skaffold/Helm with named add-ons Keycloak OIDC, Envoy Gateway) with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	19 / 20 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: 69a05eb

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.