automation-impact-analyzer-v2.0
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Analyzes the impact of PerfectScale automation on a Kubernetes namespace (or cluster/workload), CLI-first via `pscli` — the browser path is a documented fallback only, not the primary route. Use this skill whenever someone asks about automation impact, savings from automation, risk changes after enabling automation, before/after automation comparison, what automation has done, or whether automation is working. Trigger on phrases like "automation impact", "what did automation do", "before and after automation", "automation savings", "automation enabled", "automation results", "did automation help", "show me the impact", or any question combining "automation" with waste, risk, cost, savings, or namespace-level analysis.
In this repository29 other files it gives its agents.
- automation-potential-analysis-v1-v2.0Skill
- automation-potential-analysis-v2.0Skill
- backoffice-impersonationSkill
- consolidate-memorySkill
- docxSkill
- doit-slides-marpSkill
- doit-slidesSkill
- frontegg-impersonationSkill
- infrafit-improved-v2.0Skill
- 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, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
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.

