Slow system investigator
Describe a slow or failing system. Get a checked list of causes and a clear incident report.
Slow system investigator is a free AI skill for the job "Test and fix code". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · CC BY 4.0 licence · Made by sickn33 · Level: advanced · Thinking: high
Made by sickn33. See the original on GitHub; we copied it as it is, with its licence.
What it does
A short list of checked causes and a clear incident report when a server, container or app is slow or failing. Instead of running whatever commands come to mind, the skill follows a fixed method from performance expert Brendan Gregg. First it uses the USE method: for each resource such as CPU, memory, disk and network, check use, saturation and errors. Then the TSA method looks at where each thread spends its time. Each finding is tied to evidence, such as command output, so you can see why a cause was ruled in or out. The last step writes a root cause report or postmortem. It works best on Linux systems where you can run the commands.
You give it
- A description of the slow or failing system
- Access to run checks, or pasted command output
- What changed recently (optional)
- Codebase (optional)
You get
- A resource by resource checklist
- Findings with the evidence behind them
- The most likely root cause
- A written incident or postmortem report
Use it when
- A server is slow and nobody knows why.
- Latency jumped after a deploy or a config change.
- Threads pile up and your app hangs.
- You must write a postmortem and need the evidence in order.
How to use it
- Add it to your AI once: download it and add the folder to Claude, ChatGPT or Codex as a skill.
- Ask for the job in your own words. Your AI opens the skill when it fits.
- It works best when your AI can run commands on your machine.