This analyzes your Kubernetes resource configurations against actual usage patterns to tell you which containers are overprovisioned (wasting money) or underprovisioned (risking OOMKills). Run it monthly for cost optimization or after production incidents to dial in the right CPU and memory limits. The workflow assumes you're feeding it metrics as text or JSON rather than connecting directly to a live cluster, which keeps it safe for reviewing infrastructure-as-code. Skip this during initial development when you don't have real traffic data yet, and remember it's for right-sizing your baseline config, not real-time autoscaling.
npx -y skills add jorgealves/agent_skills --skill k8s-resource-optimizer --agent claude-codeInstalls into .claude/skills of the current project.
The k8s-resource-optimizer helps teams balance performance and cost. It identifies containers that are either "starving" (causing crashes) or "bloated" (wasting money) by comparing their configuration against actual usage patterns.
sickn33/antigravity-awesome-skills
kubesphere/kubesphere
supercent-io/skills-template