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.
77
78%
Does it follow best practices?
Impact
56%
0.85xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/memory-leak-debugging/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (JavaScript/Node.js memory leak diagnosis and resolution), lists concrete actions, and provides explicit trigger conditions with natural user language. It uses proper third-person voice and is concise without being vague. The description would perform well in a large skill library due to its distinctive domain and trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'diagnoses and resolves memory leaks', 'analyze heapsnapshots', 'run memory leak detection tools like memlab'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Diagnoses and resolves memory leaks in JavaScript/Node.js applications') and when ('Use when a user reports high memory usage, OOM errors, or wants to analyze heapsnapshots or run memory leak detection tools like memlab'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'memory leaks', 'high memory usage', 'OOM errors', 'heapsnapshots', 'memlab', 'JavaScript', 'Node.js'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: memory leaks specifically in JavaScript/Node.js, with unique trigger terms like 'heapsnapshots', 'memlab', and 'OOM errors' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured skill that effectively uses progressive disclosure to keep the main file focused while deferring details to reference files. Its main weaknesses are the lack of validation/feedback loops in the workflows and the limited inline actionable content—most concrete guidance is deferred to reference files that weren't provided for evaluation. The conciseness could be improved by trimming introductory filler.
Suggestions
Add explicit validation checkpoints to workflows, e.g., 'Verify snapshot file size is > 0 bytes before proceeding' and 'After applying fix, re-run memlab to confirm leak is resolved'
Include a concrete inline memlab command example (e.g., `memlab find-leaks --baseline baseline.heapsnapshot --target target.heapsnapshot --final final.heapsnapshot`) rather than deferring entirely to the reference file
Remove the introductory sentence ('This skill provides expert guidance...') as it adds no actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary explanation (e.g., 'This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks' is filler). The 'Core Principles' section has some padding like explaining what detached DOM nodes are, but overall it's reasonably tight. | 2 / 3 |
Actionability | Provides some concrete guidance (the fallback script command is executable, snapshot workflow has specific steps), but most workflows defer to reference files rather than providing inline executable examples. The memlab section is essentially 'read this other file,' and the capturing snapshots section lists tool names without concrete command syntax. | 2 / 3 |
Workflow Clarity | The four workflows are clearly sequenced and logically ordered (capture → analyze → identify → fallback). However, there are no explicit validation checkpoints or feedback loops—e.g., no step to verify snapshots were captured correctly, no guidance on what to do if memlab analysis returns no leaks, and no verification after applying fixes. | 2 / 3 |
Progressive Disclosure | Good structure with a concise overview in SKILL.md and clear one-level-deep references to memlab.md and common-leaks.md. Navigation is well-signaled with explicit links. Content is appropriately split between the main file and reference materials. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ChromeDevTools/chrome-devtools-mcp
- Commit
2e039c0
- Reviewed
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.