claudeskills.page

10 skills · 5 categories

Claude Code skills for Kubernetes

Kubernetes skills for deployments with probes and resource limits that are right, Helm charts, GitOps with Argo CD, progressive delivery and debugging pods that crash, hang or get evicted.

Install all 10 Browse the list

Start with these

  1. 1

    Kubernetes Autoscaling

    Scale on the right signal, before latency breaks

    Has Claude treat autoscaling as one system: requests set from measured usage, a scaling signal that leads saturation, HPA behavior tuned against flapping, KEDA for queues and scale to zero, and Karpenter or Cluster Autoscaler sized to provisioning time. It keeps VPA and HPA off the same metric, writes PDBs that let nodes drain, and ships a simulator that replays a load curve through the HPA math.

  2. 2

    Kubernetes Deploy

    Rollouts that finish, pods that stay up

    Claude checks the kube context before touching anything, writes Deployments with startup, readiness and liveness probes that mean different things, sizes requests from observed usage, and adds PDBs, spread constraints and a preStop drain. When pods fail it walks a status-to-cause table using describe, logs --previous and ephemeral debug containers instead of guessing.

  3. 3

    Argo CD GitOps

    Every cluster change is a reviewed, revertable commit

    Claude lays out a config repo with overlays per environment, generates Applications from ApplicationSets inside locked-down AppProjects, and orders syncs with waves and PreSync hooks. It explains OutOfSync drift instead of papering over it, keeps secrets out of Git with External Secrets or Sealed Secrets, and makes production promotion a pull request that moves one image tag.

All 10 Kubernetes skills

Grouped by category. Each card opens the full playbook, example prompts and install commands.

DevOps & SRE 6

No. 159

Kubernetes Autoscaling

Scale on the right signal, before latency breaks

Has Claude treat autoscaling as one system: requests set from measured usage, a scaling signal that leads saturation, HPA behavior tuned against flapping, KEDA for queues and scale to zero, and Karpenter or Cluster Autoscaler sized to provisioning time. It keeps VPA and HPA off the same metric, writes PDBs that let nodes drain, and ships a simulator that replays a load curve through the HPA math.

kubernetes-autoscaling 331 lines · 2 files
No. 160

Kubernetes Deploy

Rollouts that finish, pods that stay up

Claude checks the kube context before touching anything, writes Deployments with startup, readiness and liveness probes that mean different things, sizes requests from observed usage, and adds PDBs, spread constraints and a preStop drain. When pods fail it walks a status-to-cause table using describe, logs --previous and ephemeral debug containers instead of guessing.

kubernetes-deploy 225 lines · 2 files
No. 147

Argo CD GitOps

Every cluster change is a reviewed, revertable commit

Claude lays out a config repo with overlays per environment, generates Applications from ApplicationSets inside locked-down AppProjects, and orders syncs with waves and PreSync hooks. It explains OutOfSync drift instead of papering over it, keeps secrets out of Git with External Secrets or Sealed Secrets, and makes production promotion a pull request that moves one image tag.

argocd-gitops 269 lines · 2 files
No. 157

Helm Charts

Charts that render clean and upgrade safely

Claude designs a small, documented values surface with a JSON schema, writes templates on shared helpers with immutable selector labels, and adds checksum annotations so config changes roll pods. Before any upgrade it lints, renders every environment's values through kubeconform, diffs against the live release and upgrades with wait and automatic rollback.

helm-charts 242 lines
No. 148

Blue-Green and Canary Deploys

Ship gradually, roll back in one command

Claude first checks that both versions can run side by side, covering additive migrations, tolerant consumers and cron jobs that would run twice, then picks blue/green, canary or a flagged launch based on traffic. It wires per-version metric gates, shifts traffic in steps with bake time, and writes a rollback plan with triggers, commands and data caveats.

blue-green-deploys 208 lines
No. 162

Log Analysis

Count, compare to baseline, then read

Claude pins the question and a UTC window, finds the minute errors departed from normal, and groups messages into normalized signatures so new failures stand out against a baseline period. It follows a single request across services by correlation ID, lines the spike up with deploys, and reports findings with the exact queries and redacted sample lines.

log-analysis 165 lines · 2 files

Security 1

No. 273

Container Security

Minimal images, non-root pods, scanned on every build

Claude fixes container risk at the source: it swaps bloated base images for pinned distroless or slim ones, moves build secrets to BuildKit mounts, runs as a numeric non-root user, and applies a restricted securityContext with dropped capabilities and a read-only root filesystem. Trivy and hadolint gate CI, images get signed, and every change is measured against a CVE baseline.

container-security 209 lines

Performance 1

No. 299

JVM Tuning

GC logs and JFR first, then a short flag set with reasons

Claude starts by recording the JDK version, collector, heap, container limits and a stated latency goal, then gathers GC logs and a Flight Recorder capture under real load. It classifies the problem, such as humongous allocations, an undersized heap, native memory overrun or CPU throttling, fixes allocation causes before flags, and ends with a short flag set where every entry has a reason.

jvm-tuning 183 lines · 2 files

Technical Writing 1

No. 396

Runbooks

From page to mitigation without asking anyone

Claude writes one runbook per alert, starting from the alert rule itself: what it means, who is affected, then read-only triage commands with the normal output spelled out. A decision tree routes to mitigations ordered by risk, each with exact commands, expected effect, verification and undo, and high-risk steps require incident commander approval inline.

runbooks 184 lines

Automation & Tooling 1

★ No. 501

Scheduled Jobs

Cron jobs safe to rerun, overlap-proof and watched

Claude designs the job to be rerun safely before choosing a schedule, then wires it into a systemd timer, cron, launchd or a Kubernetes CronJob with catch-up, jitter and a time limit. A bundled wrapper adds a portable single-instance lock, UTC logs and healthcheck pings, and every job ships with a heartbeat monitor that alerts when it silently stops running.

scheduled-jobs 212 lines · 2 files

Install

Every Kubernetes skill in one command

Installs into ~/.claude/skills/. Add --project after -- to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- kubernetes-autoscaling kubernetes-deploy argocd-gitops helm-charts scheduled-jobs container-security runbooks blue-green-deploys log-analysis jvm-tuning

Kubernetes skills FAQ

What is the best Claude Code skill for Kubernetes?

Start with Kubernetes Autoscaling: Scale on the right signal, before latency breaks. Then add Kubernetes Deploy and Argo CD GitOps, which cover the next most common Kubernetes requests.

How do I install all 10 Kubernetes skills at once?

Pass every name to the installer in one command: curl -fsSL https://claudeskills.page/install.sh | sh -s -- kubernetes-autoscaling kubernetes-deploy argocd-gitops helm-charts scheduled-jobs container-security runbooks blue-green-deploys log-analysis jvm-tuning. Add --project to install them into the current repository's .claude/skills/ folder so your team gets them too.

Do these Kubernetes skills work outside Claude Code?

Yes. Each skill uses only the portable Agent Skills frontmatter, so the same folder works on claude.ai, through the Claude API and in the Agent SDK. Skills that run bundled scripts need an environment with code execution.

Related technologies

esc