jorgealves/agent_skills

k8s-resource-optimizer

Analyzes Kubernetes resource usage metrics and historical data to suggest optimal CPU and Memory requests and limits. Use to reduce cloud costs, prevent OOMKills, and improve overall cluster reliability by right-sizing your deployments.

First seen Jan 30, 2026

Installation

$ npx skills add jorgealves/agent_skills --skill k8s-resource-optimizer

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jorgealves/agent_skills · top by installs.

npx skills add jorgealves/agent_skills

Browse all from jorgealves/agent_skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 2
License license-compliance-auditor
Default branch main
Open issues 1
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,258 B
  • docs SUMMARY.md 1,234 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 203 installs

SKILL.md

K8s Resource Optimizer

Purpose and Intent

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.

When to Use

  • Cloud Cost Optimization: Run monthly to identify waste in your clusters.
  • Reliability Engineering: Use after a production incident involving OOMKills to find the correct memory threshold.
  • Pre-production Scaling: Set realistic requests/limits before a major launch.

When NOT to Use

  • Initial Development: Don't over-optimize before you have real traffic patterns.
  • Real-time Autoscaling: This tool is for "right-sizing" configuration; use a HPA/VPA for real-time adjustments.

Security and Data-Handling Considerations

  • No live cluster interaction required if metrics are passed as text/json.
  • Safe to run on infrastructure-as-code files.