Claude Code skills · updated 2026-10-03
Helm chart lint skill for Claude Code — Chart.yaml errors and kubeVersion EOL
Chart.yaml lines Helm rejects or rewrites, each with file:line and the fix
On the bundled sample chart: 6 findings (2 errors, 4 warnings) in 1 file from 16 rules - "v2.4" coerced to 2.4.0, appVersion 1.10 read as the number 1.1, a kubeVersion that installs only on 1.34 (end of life 2026-10-27), an "owner" field Chart.yaml does not allow.
Get it on Whop - $12 onceGet it on Gumroad
Who it's for
For platform and DevOps teams who publish or maintain Helm charts and run helm in CI.
What breaks, and when
A kubeVersion of ">=1.25.0 <1.35.0" installs only on Kubernetes 1.34, end of life 2026-10-27, and Helm 3 security fixes end 2026-11-11; extra Chart.yaml fields are not allowed as of Helm v3.3.2.
What it printed on the bundled example
== helm chart lint Chart.yaml — 6 findings (2 errors, 4 warnings) in 1 file · 16 rules
WARNING chart-sample.yaml:1 [api-v1]
apiVersion v1 is the pre-Helm-3 chart format - charts that require at least Helm 3 should say v2. Fix: apiVersion: v2
WARNING chart-sample.yaml:4 [version-coerced]
version gets coerced (leading v or fewer than 3 parts) - "v2.4" becomes 2.4.0, so the package is named <name>-2.4.0.tgz. Fix: version: 2.4.0
WARNING chart-sample.yaml:5 [appversion-unquoted]
appVersion is unquoted and YAML reads it as a number - 1.10 is read as the number 1.1. Fix: appVersion: "1.10"
WARNING chart-sample.yaml:6 [kube-eol-soon]
kubeVersion only allows Kubernetes minors reaching end of life within 90 days - ">=1.25.0 <1.35.0" installs only on 1.34, end of life 2026-10-27 (24 days after 2026-10-03). Fix: kubeVersion: ">=1.33.0-0" (no upper cap below the newest minor)
What you get
- SKILL.md, an offline Node scanner (scripts/scan.js) and the 16-rule table
- file:line, severity and the fix line for every Chart.yaml problem
- kubeVersion checked against dated Kubernetes end of life; Helm 3 pins in CI
- CI: node scripts/scan.js . exits 1 on any error
Install
Unzip into ~/.claude/skills/ (all projects) or your-repo/.claude/skills/ (one repo), then ask Claude Code: "We're cutting a new release of our Helm charts. Is anything in the Chart.yaml files going to break or get rewritten? Don't edit anything yet.". Needs Node 16+.
unzip helm-chart-lint.zip -d ~/.claude/skills/
Ask Claude
“We're cutting a new release of our Helm charts. Is anything in the Chart.yaml files going to break or get rewritten? Don't edit anything yet.”
What it does not do
It does not run helm, render templates or talk to a cluster; it reads YAML text only. No network calls, no edits without your OK.
FAQ
What is a Claude Code skill?
A folder with a SKILL.md and scripts that Claude Code loads when your request matches it. You ask in plain words and Claude runs the scanner the skill carries.
How is this different from asking Claude without the skill?
The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of answering from memory.
Does it send my code anywhere?
It does not run helm, render templates or talk to a cluster; it reads YAML text only. No network calls, no edits without your OK.
How do I install it?
Unzip into ~/.claude/skills/ (all projects) or your-repo/.claude/skills/ (one repo), then ask Claude Code: "We're cutting a new release of our Helm charts. Is anything in the Chart.yaml files going to break or get rewritten? Don't edit anything yet.". Needs Node 16+.
What do I get when I buy?
The zip. On Whop it is in your library as a download lesson with the zip attached; on Gumroad it is the product file.