detecting-memory-leaks

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill detecting-memory-leaks

Detect potential memory leaks and analyze memory usage patterns in code. Use when troubleshooting performance issues related to memory growth or identifying leak sources. Trigger with phrases like "detect memory leaks", "analyze memory usage", or "find memory issues".

57%

Overall

Validation — 81%

Implementation — 20%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill is highly verbose and abstract, explaining concepts Claude already understands while failing to provide the concrete, executable guidance needed for actual memory leak detection. It describes what the skill does rather than instructing how to do it, with no code examples, specific tool commands, or detection patterns that would make it actionable.

Suggestions

Replace abstract descriptions with concrete code examples showing actual memory leak patterns and detection techniques (e.g., specific valgrind commands, heapdump analysis code, common leak patterns in JavaScript/Python)

Remove the 'Overview', 'How It Works', and 'When to Use This Skill' sections entirely - this information is redundant with the skill description

Add executable detection scripts or commands for each leak type mentioned (event listeners, cache growth, closures) with expected output formats

Include specific validation steps in the workflow, such as 'Run valgrind --leak-check=full ./app and verify exit code 0 before proceeding'

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive padding explaining concepts Claude already knows (what memory leaks are, when to use the skill, how it works conceptually). The 'Overview', 'How It Works', and 'When to Use This Skill' sections are redundant given the skill description already covers this.	1 / 3
Actionability	No concrete code examples, commands, or executable guidance. The 'Instructions' section lists vague steps like 'Analyze code for common memory leak patterns' without showing HOW to do this. Examples describe what the skill 'will do' rather than providing actual detection code or tool commands.	1 / 3
Workflow Clarity	The Instructions section provides a numbered sequence of steps, but lacks validation checkpoints, specific tool commands, and feedback loops for error recovery. The Error Handling section exists but is generic troubleshooting rather than integrated validation steps.	2 / 3
Progressive Disclosure	Content is organized into sections but everything is inline in one monolithic file. The 'Resources' section mentions external documentation but provides no actual links. Content that could be separate (detailed patterns, tool-specific guides) is either missing or vaguely referenced.	2 / 3
	Total	6 / 12 Passed

Activation

90%

This is a well-structured skill description with strong trigger term coverage and clear completeness. The explicit 'Use when' and 'Trigger with' clauses make it easy for Claude to know when to select this skill. The main weakness is that the capability description could be more specific about what concrete actions or outputs the skill provides.

Suggestions

Add more specific concrete actions to improve specificity, such as 'identify unclosed resources, track object allocation patterns, detect circular references, generate memory usage reports'

Dimension	Reasoning	Score
Specificity	Names the domain (memory leaks, memory usage patterns) and some actions (detect, analyze), but doesn't list comprehensive concrete actions like specific analysis techniques, tools used, or output formats.	2 / 3
Completeness	Clearly answers both what (detect memory leaks, analyze memory usage patterns) and when (troubleshooting performance issues, identifying leak sources) with explicit trigger phrases provided.	3 / 3
Trigger Term Quality	Explicitly includes natural trigger phrases users would say: 'detect memory leaks', 'analyze memory usage', 'find memory issues', plus mentions 'performance issues' and 'memory growth' which are common user terms.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on memory leaks and memory usage analysis. The specific triggers ('memory leaks', 'memory growth', 'leak sources') are distinct and unlikely to conflict with general code analysis or other performance skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.