CtrlK
BlogDocsLog inGet started
Tessl Logo

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 capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.

82

4.13x
Quality

85%

Does it follow best practices?

Impact

95%

4.13x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and uses progressive disclosure effectively with a verified reference file. Its weakest area is workflow clarity, where the heap-snapshot workflow could use explicit validation/feedback loops given the cost of these operations.

Suggestions

Add an explicit validate→fix→retry feedback loop to the capture/compare workflow (e.g., 'if a snapshot fails to load, re-capture and re-run compare_heapsnapshots').

Add a checkpoint after compare_heapsnapshots to confirm the diff shows meaningful growth before drilling into retainers, to avoid wasted inspection.

Trim the restated intro paragraph and the duplicated emphasis on closing snapshots to tighten token efficiency.

DimensionReasoningScore

Conciseness

Efficiently lists MCP tools and parameters without explaining basic concepts, though the opening line restates the description and a few phrasings could be trimmed.

4 / 5

Actionability

Names specific tools, parameters (classIndex, filterName), and named leak-category filters, giving mostly executable guidance; guidance is instruction-based rather than literal copy-paste code.

4 / 5

Workflow Clarity

A clear four-phase sequence (capture, compare, inspect, advanced) with implicit checkpoints like 'confirm that the files load' and 'before changing code', though it lacks an explicit validate→fix→retry feedback loop for these expensive batch operations.

4 / 5

Progressive Disclosure

Well-organized overview with a clearly signaled, one-level-deep reference to the real references/common-leaks.md file, keeping detail out of SKILL.md.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions, with concrete actions, explicit trigger guidance, and a distinct niche. The only minor gap is a few missing natural synonyms and the .heapsnapshot extension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Diagnoses and resolves memory leaks', 'capture, compare, or inspect heap snapshots' — with a named toolset, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what it does and when to use it via the concrete 'Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots' trigger phrase.

5 / 5

Trigger Term Quality

Natural user-facing terms like 'high memory usage', 'OOM errors', and 'heap snapshots' are present, but it lacks synonyms and the .heapsnapshot file extension users might mention.

4 / 5

Distinctiveness Conflict Risk

Scoped to JavaScript/Node.js heap-snapshot debugging via Chrome DevTools MCP, a clear niche with minimal overlap against other skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ChromeDevTools/chrome-devtools-mcp
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.