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".
54
44%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/memory-leak-detector/skills/detecting-memory-leaks/SKILL.mdQuality
Discovery
89%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 solid skill description with excellent trigger terms and completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the capability description could be more specific about the concrete actions performed (e.g., heap profiling, reference tracking, allocation analysis). Overall it would perform well in a multi-skill selection scenario.
Suggestions
Add more specific concrete actions such as 'track heap allocations', 'identify unreleased references', 'analyze garbage collection patterns' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (memory leaks, memory usage) and some actions (detect, analyze), but doesn't list multiple concrete specific actions beyond detecting and analyzing. It lacks specifics like 'track allocations', 'identify unreleased references', 'profile heap usage', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (detect potential memory leaks and analyze memory usage patterns) and 'when' (troubleshooting performance issues related to memory growth, identifying leak sources) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'detect memory leaks', 'analyze memory usage', 'find memory issues', 'performance issues', 'memory growth', 'leak sources'. These are phrases users would naturally say when encountering memory problems. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to memory leak detection and memory usage analysis, which is a distinct niche. The specific trigger terms around 'memory leaks', 'memory usage', and 'memory growth' make it unlikely to conflict with general performance or code analysis skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is almost entirely descriptive rather than instructive. It explains what memory leak detection is and describes what the skill would do at a high level, but provides zero concrete patterns to search for, no code examples of actual leaks or detection techniques, and no executable commands. It reads more like a product marketing page than an actionable skill for Claude.
Suggestions
Replace the abstract descriptions with concrete code examples of common memory leak patterns (e.g., Node.js event listener leaks, Python circular references, unbounded dict caches) and their fixes.
Add specific detection steps with actual code or commands, such as grep patterns for common leak signatures, heap snapshot analysis commands, or static analysis approaches.
Remove the 'Overview', 'How It Works', 'When to Use This Skill', 'Integration', and 'Resources' sections entirely — they explain concepts Claude already knows and add no actionable value.
Add a concrete report template/format showing exactly what the output should look like, with example file locations, severity ratings, and code-level fix recommendations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections explaining things Claude already knows (what memory leaks are, when to use the skill, how it works at a high level). Sections like 'Overview', 'How It Works', 'When to Use This Skill', 'Integration', and 'Resources' add almost no actionable value and waste tokens on obvious concepts. | 1 / 3 |
Actionability | No concrete code examples, no executable commands, no specific patterns to look for. The 'Instructions' section is a vague checklist ('Analyze code for common memory leak patterns') without specifying what those patterns are or how to detect them. The examples describe what the skill 'will do' rather than showing how to actually do it. | 1 / 3 |
Workflow Clarity | The workflow steps are abstract and lack any validation checkpoints. 'Analyze code for common memory leak patterns' and 'Generate report with leak locations' give no concrete sequence of actions, no specific tools/commands to run, and no feedback loops for verifying findings. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Multiple sections that could be consolidated or removed entirely. The content is poorly organized with redundant sections (Overview, How It Works, When to Use, Examples all overlap significantly). | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3e83543
- 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.