detecting-memory-leaks
This skill enables Claude to detect potential memory leaks and analyze memory usage patterns in code. It is triggered when the user requests "detect memory leaks", "analyze memory usage", or similar phrases related to memory leak detection and performance analysis. The skill identifies potential issues such as unremoved event listeners, closures preventing garbage collection, uncancelled timers, unbounded cache growth, circular references, detached DOM nodes, and unnecessary global state accumulation. It then provides detailed fix recommendations. Use this skill to proactively identify and resolve memory leaks, improving application performance and stability.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill detecting-memory-leaks63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms developers would use, explicitly states both what the skill does and when to use it, and carves out a distinct niche in memory leak detection that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'detect potential memory leaks', 'analyze memory usage patterns', and identifies specific issues like 'unremoved event listeners, closures preventing garbage collection, uncancelled timers, unbounded cache growth, circular references, detached DOM nodes, and unnecessary global state accumulation'. | 3 / 3 |
Completeness | Clearly answers both what (detect memory leaks, analyze patterns, identify specific issues, provide fix recommendations) AND when ('triggered when the user requests "detect memory leaks", "analyze memory usage"' and 'Use this skill to proactively identify and resolve memory leaks'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'detect memory leaks', 'analyze memory usage', 'memory leak detection', 'performance analysis'. These are terms developers naturally use when seeking this type of help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on memory leak detection and memory usage analysis. The specific technical triggers ('memory leaks', 'garbage collection', 'event listeners') make it unlikely to conflict with general code analysis or other performance skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a marketing description rather than actionable guidance. It describes what the skill does conceptually but provides zero concrete implementation details—no code patterns to detect, no specific analysis techniques, no example leak patterns with fixes. Claude would gain no actionable knowledge from this content.
Suggestions
Add concrete code examples showing actual memory leak patterns (e.g., unremoved event listeners, closure leaks) with before/after fix code
Provide specific detection heuristics or patterns Claude should look for when analyzing code (e.g., 'addEventListener without corresponding removeEventListener')
Include example analysis output format showing how to structure memory leak reports with severity, location, and fix recommendations
Remove the 'How It Works', 'When to Use', and 'Best Practices' sections which explain concepts Claude already understands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what memory leaks are, basic workflow descriptions). Phrases like 'This skill helps you identify and resolve memory leaks' and 'How It Works' sections add no actionable value. | 1 / 3 |
Actionability | No concrete code examples, commands, or executable guidance provided. The examples describe what the skill 'will do' abstractly rather than showing actual detection patterns, code snippets, or specific analysis techniques Claude should apply. | 1 / 3 |
Workflow Clarity | The workflow is vague ('analyze the codebase', 'generate a report') with no specific steps, validation checkpoints, or concrete analysis procedures. No actual detection patterns or code analysis techniques are specified. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic file with no references to detailed materials. The structure exists but contains no substantive content that would benefit from progressive disclosure. | 2 / 3 |
Total | 5 / 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.
- 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.