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.

1.37x

Quality

85%

Does it follow best practices?

Impact

92%

1.37x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

82%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.

A well-structured, highly actionable instruction-only skill: concrete tool names and parameters throughout, a clear four-phase workflow with validation checkpoints, and an appropriate one-level reference. Minor improvements possible by removing the small overlap between the inline culprit list and the common-leaks reference, and stating error-recovery paths.

Dimension	Reasoning	Score
Conciseness	The body is lean and tool-focused with no padding about what memory leaks are, but the opening sentence "This skill provides expert guidance and workflows for..." and the inline "Common Culprits" list (which duplicates references/common-leaks.md) could be trimmed. Efficient with minor over-explanation, matching the 4 anchor rather than the every-token-earns-its-place 5 anchor.	4 / 5
Actionability	Names exact MCP tools with their parameters (`take_heapsnapshot` with `pageId`, `compare_heapsnapshots` with/without `classIndex`, `get_heapsnapshot_object_details` with `nodeId`, `filterName` values) plus concrete tactics like "Repeat the same user interactions 10 times". This is fully actionable instruction-only guidance covering the common cases.	5 / 5
Workflow Clarity	Four clearly sequenced workflows (capture → compare → inspect retainers → categorized filters) with an explicit load-validation checkpoint ("Start with get_heapsnapshot_summary... to confirm that the files load") and a revert-to-baseline check. Not a 5 because error-recovery loops (e.g., what to do when a snapshot fails to load or the diff shows nothing) are not spelled out.	4 / 5
Progressive Disclosure	Well-organized sections with one clearly signaled, one-level-deep reference ([references/common-leaks.md](references/common-leaks.md), verified to exist) placed at a logical point with its purpose stated. The inline "Common Culprits" bullets partially duplicate that reference file, a minor organization gap that keeps it below the 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

A strong description: concrete third-person capabilities paired with an explicit 'Use when...' clause containing realistic trigger phrases. The only weakness is slightly thinner synonym coverage (e.g., missing file extensions or terms like 'memory growth').

Dimension	Reasoning	Score
Specificity	"Diagnoses and resolves memory leaks", "capture, compare, or inspect heap snapshots" lists several concrete third-person actions with only minor coverage gaps (no mention of fix verification). Fits the 'several specific actions; minor gaps' anchor, not the 5 anchor's fully comprehensive coverage.	4 / 5
Completeness	Explicitly answers 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 capture, compare, or inspect heap snapshots...") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Natural user phrases like "high memory usage", "OOM errors", "memory leaks", and "heap snapshots" are present, matching the good-coverage anchor. Not a 5 because common variations such as "memory growth", "RSS/node memory", or the .heapsnapshot extension are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (JS/Node memory leaks via Chrome DevTools MCP heap-snapshot tooling) with distinct triggers like "OOM errors" and "heap snapshots"; minimal overlap with general profiling or performance skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ChromeDevTools/chrome-devtools-mcp
Path: skills/memory-leak-debugging/SKILL.md
Commit: 02c0112

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.