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".

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/memory-leak-detector/skills/detecting-memory-leaks/SKILL.md

Quality

Content

0%Weight 40%Scale 1-3

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

The content is largely descriptive prose that restates general knowledge rather than providing executable, leak-specific guidance. It lacks concrete code, validation steps, and any linking to the bundle files that exist alongside it, leaving Claude without actionable direction.

Suggestions

Replace the abstract 'Instructions' list with executable examples: concrete code snippets or commands for finding unremoved event listeners, unbounded caches, and retained closures in Node.js, Python, and JVM.

Add validation/feedback checkpoints to the workflow (e.g., confirm a suspected leak reproduces under a profiler before reporting it, and re-measure after applying a fix).

Link to the bundled scripts (analyze_memory.py, generate_report.py, setup_environment.py) and references/assets from the relevant sections instead of leaving them unmentioned in the body.

Dimension	Reasoning	Score
Conciseness	The body pads generic sections ('Overview', 'How It Works', 'Best Practices', 'Integration', 'Prerequisites') that restate what Claude already knows about memory leaks rather than adding concrete detection knowledge, matching the verbose score-1 anchor.	1 / 3
Actionability	Instructions like 'Analyze code for common memory leak patterns' and 'Identify unremoved event listeners' describe tasks abstractly with no executable code or commands, matching the score-1 'describes rather than instructs' anchor.	1 / 3
Workflow Clarity	The 'Instructions' section is a flat six-step list with no validation checkpoints or feedback loops for what is a batch analysis operation, matching the score-1 anchor for missing sequence rigor and validation.	1 / 3
Progressive Disclosure	The body is a monolithic wall of generic sections and never signals the bundled scripts, references, or assets that exist on disk, so navigation to those deeper materials is effectively absent.	1 / 3
	Total	4 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 well-constructed: it states the skill's purpose, gives explicit 'Use when' trigger guidance, and lists natural trigger phrases. Its only weakness is that the stated capabilities are somewhat broad rather than enumerating a comprehensive list of concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain and two actions ('Detect potential memory leaks and analyze memory usage patterns in code') but does not list a comprehensive set of concrete actions, matching the score-2 anchor.	2 / 3
Completeness	It clearly answers what the skill does and provides an explicit 'Use when...' clause with trigger phrases, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural user phrasings are explicitly listed ('detect memory leaks', 'analyze memory usage', 'find memory issues'), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Memory leak detection is a focused niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/memory-leak-detector/skills/detecting-memory-leaks/SKILL.md
Commit: 8585d6d

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.