perf-diagnosis
Skill1 starsChanged 2 days agoLicence not identifiedView on GitHub
Diagnoses an app's performance by measuring before changing anything. Finds the bottleneck (a process's CPU, the database, the event loop, the pool, an upstream), says how it was checked (path:line + measurement) and, when the measurement is missing, says what to measure and how locally (k6, think time, p95/p99, CPU per process) before proposing a cache, another runtime, scaling or load balancing. Reports and stops. Use it for "my app is slow", "why is this endpoint slow?", "how many users can my server handle", "find the bottleneck", "load test this", "is it the database or the CPU?", "p99 is spiking", "should I add caching", "should I switch to Bun?", "hot partition", "add a cache node", even without the word "performance". Other topics go to architecture-review, infra-review, code-structure, data-consistency, api-security-review, correctness-review. Also triggers on Spanish requests such as "la app va lenta", "¿cuántos usuarios aguanta mi servidor?", "encuentra el cuello de botella" or "¿pongo Redis?".
- Reads credentials
In this repository10 other files it gives its agents.
- api-security-reviewSkill
- apply-remediationSkill
- architecture-reviewSkill
- code-structureSkill
- correctness-reviewSkill
- data-consistencySkill
- implicit-state-machinesSkill
- infra-reviewSkill
- llm-app-reviewSkill
- repo-audit-swarmSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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 350,495 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.