performance-investigation
Skill0 starsChanged 2 months agoMITView on GitHub
Diagnose latency, throughput, CPU, memory, allocation, lock contention, storage, and network regressions with measurement-first analysis. Use for benchmarks, profiles, scalability limits, and production performance problems.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- cormacc/dotagentstheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- ericwang200608-beep/LANYANT-Skillstheir own version, first seen Nov 8, 2026
- itsofficialadi/boundifftheir own version, first seen Oct 25, 2026
- sveltejs/sveltetheir own version, first seen Oct 8, 2026
- adamentwistle/fable-skillstheir own version, first seen Sep 3, 2026
Used with
Projects with it also use security-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- sveltejs/svelte★ 89ksame name
- microsoft/sre-agent★ 187same name
- REPOZY/superpowers-optimized★ 146same name
- adamentwistle/fable-skills★ 98same name
- ericwang200608-beep/LANYANT-Skills★ 2same name
- cormacc/dotagents★ 1same name
- motao123/dev-workflow-kit★ 1same name
- gclm/super-stack★ 0same name
- itsofficialadi/boundiff★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cpp-reliabilitySkill
- distributed-systems-debuggingSkill
- incident-responseSkill
- pull-requestSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Do not compare results produced by materially different workloads.
- Distinctive: line 43
Avoid optimizing from intuition or isolated microbenchmarks.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Performance investigation
Define the problem
Record:
- User-visible metric and target.
- Baseline and regression size.
- Workload, concurrency, dataset, and environment.
- Measurement window and statistical variation.
- Relevant code, configuration, dependency, or traffic changes.
Do not compare results produced by materially different workloads.
Decompose the cost
Break the path into:
- Queueing and scheduling.
- CPU and instruction cost.
- Allocation and memory pressure.
- Synchronization and contention.
- Storage and filesystem I/O.
- Network transfer and remote dependency time.
- Retries, timeouts, and duplicated work.
Gather evidence
Prefer:
- Profiles and traces.
- Histograms and percentiles.
- Hardware and runtime counters.
- Allocation and lock-contention data.
- Controlled A/B experiments.
Avoid optimizing from intuition or isolated microbenchmarks.
Recommend an optimization
Include:
- Identified bottleneck.
- Supporting measurement.
- Proposed change.
- Expected effect and assumptions.
- Correctness and operational risks.
- Benchmark and production validation plan.
- Rollback or disablement strategy.
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.