infrafit-improved-v2.0
Skill0 starsChanged 2 months agoNo licenceView on GitHub
PerfectScale InfraFit unevictable pods audit — CLI-first via `pscli`. Queries the target cluster's node groups and unevictable pods directly through the public API, classifies every blocking pod (including a workload-origin cross-check for high-volume emptyDir findings), and produces a customer-ready remediation report with exact kubectl/Helm fix syntax. Falls back to the PerfectScale UI only for auth-token generation and for snapshots that are still processing. Use for: nodes that won't drain or scale down, Cluster Autoscaler or Karpenter unable to consolidate, idle node costs not dropping, PDB or anti-affinity blockers, or why PerfectScale isn't capturing InfraFit savings. Triggers on: "unevictable pods", "infrafit", "infra fit", "node idle", "nodes won't drain", "CAS blocking", "autoscaler can't scale down", "what's blocking savings", "idle costs", "why can't nodes drain", "karpenter won't consolidate", "why are nodes idle", "nodes stuck", "blocking the autoscaler". Always use this skill when the user mentions idle node costs, drain failures, or autoscaler blockers in a PerfectScale context — even if they just name a cluster.
In this repository29 other files it gives its agents.
- automation-impact-analyzer-v2.0Skill
- automation-potential-analysis-v1-v2.0Skill
- automation-potential-analysis-v2.0Skill
- backoffice-impersonationSkill
- consolidate-memorySkill
- docxSkill
- doit-slides-marpSkill
- doit-slidesSkill
- frontegg-impersonationSkill
- kubernetes-prospect-researchSkill
- kubernetes-skillSkill
- morningSkill
- pdfSkill
- perfectscale-automation-blockers-v2.0Skill
- perfectscale-batch-analyzer-v2.0Skill
- perfectscale-cliSkill
- perfectscale-cost-savings-trendsSkill
- perfectscale-debug-analyzer-v2.0Skill
- perfectscale-hybrid-savings-analysis-v2.0Skill
- perfectscale-infrafit-analysis-v2.0Skill
- perfectscale-optimization-planSkill
- perfectscale-podfit-deployment-audit-v2.0Skill
- perfectscale-tenant-savings-report-v2.0Skill
- pptxSkill
- scheduleSkill
- setup-coworkSkill
- skill-creatorSkill
- ui-based-savings-analysisSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

