From nexus
Routes performance investigations to memory-leak or dependency-blast-radius workflows. Trigger on OOM, profiling, regression reports, or upgrade-impact questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nexus:performanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Route to the correct sub-skill and follow it end-to-end.
Route to the correct sub-skill and follow it end-to-end.
memory-leak.md, dependency-blast-radius.mdexamples/production-scenarios.md, checklists/performance-checklist.md,
heuristics/performance-heuristics.md, anti-patterns/common-mistakes.md,
validation/output-validation.mdnexus:debugging for single-service runtime failuresroadmap-planner agent after the fix is approvedPick exactly one track:
| Track | Signal | Sub-skill |
|---|---|---|
| Memory Leak | "memory growing", "OOM kill", "heap dump", "RSS increasing", "memory usage creeping up", process being killed by the OS | memory-leak.md |
| Dependency Blast Radius | "upgrade X to version Y", "what breaks if I upgrade", "which services use this lib", "blast radius of upgrading", "safe to upgrade?", "dependency impact analysis" | dependency-blast-radius.md |
If the request does not clearly fit one track, ask one question: "Is this about memory/CPU/latency behavior of a running service, or about the risk of upgrading a dependency?"
Read the appropriate sub-skill file. Follow its numbered steps in order. Do not skip steps.
Read heuristics/performance-heuristics.md for fast pattern-matching before starting investigation.
Before presenting results, check against validation/output-validation.md.
Each sub-skill defines its own output format. This router produces no standalone output.
"Memory usage is growing by 50MB per hour and the process gets OOM killed every 12 hours"
→ route to memory-leak.md
"We want to upgrade SQLAlchemy from 1.4 to 2.0 — what will break?"
→ route to dependency-blast-radius.md
"Our API latency is 3× higher than yesterday after the last deploy"
→ route to memory-leak.md if memory metrics are elevated; otherwise route to nexus:debugging
"Which of our services import requests==2.28.0 and would be affected by this CVE patch upgrade?"
→ route to dependency-blast-radius.md
npx claudepluginhub aayushostwal/nexus --plugin nexusDetects performance bottlenecks in CPU, memory, I/O, database, and lock contention layers. Provides analysis and remediation strategies for slow applications.
Profiles system performance to identify bottlenecks using measurement before optimization — follows Brendan Gregg's USE Method and Google pprof methodology.
Diagnoses slow code, APIs, queries, memory growth, frontend load, build regressions, and scalability limits using a structured measurement-based workflow.