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.

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 you get
• SKILL.md, an offline Node scanner (scripts/scan.js) and the 16-rule table

See it first
The real output of the bundled example is on getreadystack.com/skills/helm-chart-lint/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, 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 it does not do
It does not run helm, render templates or talk to a cluster; it reads YAML text only.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “helm-chart-lint.zip”.