npx skills add smithery/neversight --skill k8s-resource-optimizer
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.
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.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
3.3M installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…
568.3K installsAlso in this package
Other skills from jorgealves/agent_skills · top by installs.
npx skills add 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.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,258 B -
docs
SUMMARY.md1,234 B
History
- First seen on skills.sh
- 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.