On the bundled sample: 11 findings (9 errors, 2 warnings) in 1 file from 15 rules, including Deployment on extensions/v1beta1, CronJob on batch/v1beta1, HorizontalPodAutoscaler on autoscaling/v2beta2 and PodSecurityPolicy.

Who it’s for
For teams upgrading Kubernetes clusters or maintaining Helm charts and manifests.

What breaks, and when
Kubernetes 1.16 removed extensions/v1beta1 Deployments and 1.25 removed batch/v1beta1 CronJob and PodSecurityPolicy; a manifest that still uses them is rejected when you apply it after the upgrade.

What you get
• SKILL.md, an offline Node scanner (scripts/scan.js) and the 15-rule table

See it first
The real output of the bundled example is on getreadystack.com/skills/kubernetes-deprecated-api-check/ — 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 upgrading our Kubernetes cluster next month. Will the manifests in this repo still apply? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
It does not talk to your cluster or render Helm/Kustomize; 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 “kubernetes-deprecated-api-check.zip”.