CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/helm-dev-environment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 exceptionally actionable — every workflow ships exact commands, flags, and defaults — and the core startup/teardown sequence is clear. Its main weaknesses are token bloat and the total absence of progressive disclosure: roughly a third of the file is specialized HA/e2e/add-on detail that belongs in separate reference files rather than in every invocation's context.

Suggestions

Move the shared-supervisor HA deep-dive, the Kubernetes E2E notes, and the SPIRE/Vault/Keycloak add-on guides into separate reference files under references/ (e.g. references/supervisor-ha.md, references/e2e.md, references/add-ons.md), keeping SKILL.md to a concise overview with one-level-deep pointers.

Trim inline operational minutiae such as HPA memory thresholds, PodDisruptionBudget/rolling-update parameters, and log-grep recipes down to the command that exercises each behavior, leaving the parameter enumeration to the chart's values documentation.

Restructure so the numbered startup steps (create cluster → deploy → forward) run contiguously, and add a pre-delete check (e.g. confirming no running sandboxes or noting that helm:skaffold:delete preserves the cluster) before the destructive teardown commands.

DimensionReasoningScore

Conciseness

The ~690-line body inlines dense operational minutiae — HPA thresholds, PodDisruptionBudget flags, log-grep recipes, rollout compatibility rules — in long prose walls like the shared-supervisor HA section, so a third of the file is padded detail most invocations never need. It avoids explaining concepts Claude already knows, but the verbosity is widespread rather than occasional, matching anchor 2.

2 / 5

Actionability

Nearly every section gives copy-paste-ready commands with defaults and env vars ("mise run helm:k3s:create", the full mTLS cert-extraction block, the HA probe sequence), and the examples cover all common cases from create to teardown. The single "..." placeholder in the BackendTLSPolicy block is a trivial gap that does not disqualify the fully-executable anchor.

5 / 5

Workflow Clarity

The startup sequence is explicitly numbered with verification steps ("confirm that the gateway is registered and active", "same PID" checks) and a lint fix-retry loop, but ~150 lines of supervisor and e2e digression sit between step 1 and step 2, burying the core flow, and destructive teardown lacks any pre-check — clear sequence with minor validation gaps rather than anchor 5.

4 / 5

Progressive Disclosure

There are no bundle files at all: supervisor HA deep-dives, e2e notes, and the SPIRE/Vault/Keycloak add-on guides are all inlined in one monolithic SKILL.md. Section headers and the Key Files table provide genuine structure, so it is above the minimal-structure anchor 2, but content that clearly belongs in separate one-level-deep reference files is inline, capping it at anchor 3.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description with explicit what/when structure and an unusually thorough natural-language trigger list. Its only weakness is that coverage stops at cluster lifecycle and add-ons, leaving the e2e testing, chart linting, and tracing portions of the skill undescribed and untriggered.

DimensionReasoningScore

Specificity

Lists concrete actions ("Start up, tear down, and configure") with named tools and coverage areas (cluster lifecycle, Keycloak OIDC, Envoy Gateway, HA testing, port mappings), but omits substantial parts of the skill body such as the Kubernetes e2e suites, Helm chart lint checks, and trace viewing — more than a trivial coverage gap, so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both "what" ("Start up, tear down, and configure the local Kubernetes development environment for OpenShell") and "when" via an explicit trigger-keywords clause with concrete phrases, mirroring the anchor-5 pattern of clear what plus concrete trigger phrases.

5 / 5

Trigger Term Quality

Nineteen natural trigger terms with good synonym coverage ("local cluster", "dev cluster", "k8s dev", "helm:k3s"), but whole body subsections lack any trigger (no "e2e", "helm lint", "tracing", or "otel"), matching the "good coverage, a few natural terms missing" anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to "OpenShell" with a distinctive toolchain (k3d, Skaffold, Helm) and highly specific triggers like "helm:k3s" and "envoy gateway local", giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (697 lines); consider splitting into references/ and linking

Warning

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

12

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/helm-dev-environment/SKILL.md

Reviewed

Table of Contents

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.