memory-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.
81
85%
Does it follow best practices?
Impact
56%
0.85xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
5%
-3%Memory Leak Investigation: Growing Heap in Production Service
Memlab heap analysis with 3 snapshots
Uses npx memlab find-leaks
0%
0%
--baseline flag present
0%
0%
--target flag present
0%
0%
--final flag present
0%
0%
No raw file reading
0%
0%
Findings documented
53%
33%
75%
-20%Memory Growth Analysis: Identify Leaking Objects Between Two Snapshots
Fallback compare_snapshots.js usage
Uses compare_snapshots.js
80%
0%
No direct snapshot reading
100%
100%
Identifies growing object type
100%
100%
Reports quantitative growth
100%
100%
93%
-7%Memory Leak Code Review: Navigation Panel Component
Detached DOM nodes and event listener fixes
Identifies event listener leak
100%
100%
Recommends removeEventListener
100%
100%
Identifies detached DOM concern
100%
100%
Does not auto-fix DOM cache
100%
85%
Flags intentional cache possibility
100%
80%
Leak classification correct
100%
100%
Retainer trace referenced
100%
100%
- Repository
- ChromeDevTools/chrome-devtools-mcp
- Commit
1b857c9
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.