performance
/performance
Use for memory, CPU, latency, and query-performance investigations, plus dependency-upgrade blast-radius analysis. Trigger on leak/OOM/profiling/regression reports or "what breaks if I upgrade X." Route to memory-leak or dependency-blast-radius workflow based on intent.
- Author
- aayushostwal ↗
- Repository
- nexus ↗
- Licence
- MIT
- Last repository change
- 30.09.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use for memory, CPU, latency, and query-performance investigations, plus dependency-upgrade blast-radius analysis. Trigger on leak/OOM/profiling/regression reports or "what breaks if I upgrade X." Route to memory-leak or dependency-blast-radius workflow based on intent.
Triggers from the description
Original author description
Use for memory, CPU, latency, and query-performance investigations, plus dependency-upgrade blast-radius analysis. Trigger on leak/OOM/profiling/regression reports or "what breaks if I upgrade X." Route to memory-leak or dependency-blast-radius workflow based on intent.
How it works
- Compatibility
- Routing
- Output Format
- Anti-Patterns
- Examples
SKILL.md preview
--- name: performance description: > Use for memory, CPU, latency, and query-performance investigations, plus dependency-upgrade blast-radius analysis. Trigger on leak/OOM/profiling/regression reports or "what breaks if I upgrade X." Route to memory-leak or dependency-blast-radius workflow based on intent. --- # Nexus Performance Route to the correct sub-skill and follow it end-to-end. --- ## Compatibility - Sub-skills: `memory-leak.md`, `dependency-blast-radius.md` - Supporting files: `examples/production-scenarios.md`, `checklists/performance-checklist.md`, `heuristics/performance-heuristics.md`, `anti-patterns/common-mistakes.md`, `validation/output-validation.md` - Required tools: Read, Bash, Grep - Hands off to: `nexus:debugging` for single-service runtime failures - Hands off to: the `roadmap-planner` agent after the fix is approved --- ## Routing ### Step 1 — Classify the Request Pick 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?" ### Step 2 — Read Sub-Skill and Execute 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. ### Step 3 — Validate Output Before presenting results, check against `validation/output-validation.md`. --- ## Output Format Each sub-skill defines its own output format. This router produces no standalone output. --- ## Anti-Patterns - Never profile a running production process without confirming the profiling overhead is acceptable. - Never recommend a dependency upgrade without completing the blast radius analysis first. - Never mix tracks — complete one sub-skill fully before considering another. - Never skip reading the actual code or configuration — performance issues are almost always specific to the exact version and usage pattern. - Never recommend "just increase memory/CPU limits" without first identifying the root cause — scaling a leak just delays the next OOM. --- ## Examples **"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`
Files in this package (8)
- SKILL.md 3 KB
- dependency-blast-radius.md 10 KB
- memory-leak.md 11 KB
- anti-patterns/common-mistakes.md 1 KB
- checklists/performance-checklist.md 4 KB
- examples/production-scenarios.md 1 KB
- heuristics/performance-heuristics.md 1 KB
- validation/output-validation.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · aayushostwal/nexus | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| davila7/claude-code-templates | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| arxdsilva/ai-loops | 100 | MIT |
Database snapshot: 13.11.2026 · package version 99232c2098cc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100performance-review
Performance optimization analysis: CPU/memory profiling, caching strategies, database query optimization, connection pooling, concurrency patterns, memory leak detection, and throughput improvement. Use when code is slow, memory usage is high, latency needs reduction, or… - 100performance-profiler
Performance profiling for Node.js, Python, and Go: CPU flamegraphs, memory leak detection, bundle analysis, query optimization, and k6 load testing. Use when diagnosing slow endpoints, memory growth, large bundles, or traffic spikes. - 100performance-expert
Expert performance optimization across CPU, memory, I/O, and rendering. Trigger keywords: performance, slow, profiling, profiler, optimize, latency, throughput, p99, memory leak, allocation, bottleneck, benchmark, flamegraph, N+1, cache. Use to diagnose and fix performance… - 95memory-leak-debugging
Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to analyze heapsnapshots or run memory leak detection tools like memlab. - 95nodejs-profiling
Node.js performance profiling with V8 CPU profiler, heap analysis, and perf_hooks. Use for identifying bottlenecks and memory leaks. USE WHEN: user mentions "Node.js performance", "profiling", "memory leak", asks about "V8 profiler", "heap snapshot", "CPU profile", "perf_hooks",… - 100profiling-application-performance
Execute this skill enables AI assistant to profile application performance, analyzing cpu usage, memory consumption, and execution time. it is triggered when the user requests performance analysis, bottleneck identification, or optimization recommendations. the... Use when…