perfectscale-debug-analyzer-v2.0
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Builds a Claude-powered interactive coaching tool for analyzing PerfectScale workload zoom-in debug JSON payloads. Runs a `pscli` pre-check for quick current/recommended/indicator context, but the core reasoning-chain payload (cpuReasoning, memReasoning, indicatorReasoning) is internal-only and still requires the browser debug modal — confirmed absent from the public API. Use this skill whenever someone wants to analyze a PerfectScale debug payload, understand why PerfectScale made a specific recommendation, coach a customer on workload optimization findings, or create an internal tool for the technical team to interpret PerfectScale reasoning chains. Also trigger when users say things like "analyze this workload", "explain this PerfectScale recommendation", "build the debug analyzer", "create a coaching tool for PerfectScale", or upload/paste a JSON file that contains PerfectScale recommendation fields like "recommendations", "revisions", "mergedRevision", "indicatorReasoning", or "cpuReasoning".
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
- 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-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
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 13 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
11
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.

