Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jorgealves avatar

K8s Resource Optimizer

  • 186 installs
  • 2 repo stars
  • Updated January 25, 2026
  • jorgealves/agent_skills

Right-size Kubernetes CPU and memory requests and limits using utilization signals to cut cluster cost and reduce eviction risk on production workloads.

About

k8s-resource-optimizer inspects Kubernetes workload manifests and runtime signals to recommend tighter CPU and memory requests, limits, and QoS classes. It targets cost reduction, fewer evictions, and more predictable autoscaling while preserving headroom for bursty services in production clusters.

  • Analyzes pod utilization versus declared requests
  • Recommends safer limit-to-request ratios
  • Identifies over-provisioned Deployments and StatefulSets
  • Flags OOMKill and throttle hotspots
  • Suggests incremental rollout-friendly changes

K8s Resource Optimizer by the numbers

  • 186 all-time installs (skills.sh)
  • +8 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #466 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jorgealves/agent_skills --skill k8s-resource-optimizer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs186
repo stars2
Last updatedJanuary 25, 2026
Repositoryjorgealves/agent_skills

What it does

Right-size Kubernetes CPU and memory requests and limits using utilization signals to cut cluster cost and reduce eviction risk on production workloads.

Files

SKILL.mdMarkdownGitHub ↗

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.

Related skills

Cloud & Infrastructureinframonitoringdeploy

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.