heap-dump-analyzer
Heap Dump Analyzer - Auto-activating skill for Performance Testing. Triggers on: heap dump analyzer, heap dump analyzer Part of the Performance Testing skill category.
35
3%
Does it follow best practices?
Impact
92%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/heap-dump-analyzer/SKILL.mdQuality
Discovery
7%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 description is essentially a label rather than a functional description. It names the skill and its category but provides no concrete actions, no meaningful trigger terms, and no explicit guidance on when Claude should select it. It reads like auto-generated boilerplate with a duplicated trigger term.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Parses Java heap dumps (.hprof files), identifies memory leaks, analyzes object retention graphs, and reports dominant memory consumers.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions heap dumps, memory leaks, OutOfMemoryError, OOM, .hprof files, memory profiling, or GC analysis.'
Remove the duplicated trigger term ('heap dump analyzer' is listed twice) and expand with varied natural language terms users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Heap Dump Analyzer', 'Performance Testing') but does not describe any concrete actions. There are no specific capabilities listed such as 'parse heap dumps', 'identify memory leaks', 'analyze object retention', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just a repeated label, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'heap dump analyzer' repeated twice, which is redundant. It misses natural user terms like 'memory leak', 'heap analysis', 'OOM', 'out of memory', 'memory profiling', '.hprof', 'GC issues', or 'object retention'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'heap dump' is fairly niche and unlikely to conflict with many other skills, but the lack of specificity about what it actually does and the generic 'Performance Testing' category could cause overlap with other performance-related skills. | 2 / 3 |
Total | 5 / 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 an empty template/placeholder that contains no actual instructional content about heap dump analysis. It merely describes when it should activate and repeats the phrase 'heap dump analyzer' without providing any concrete guidance, tools, commands, or workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples for capturing heap dumps (e.g., `jmap -dump:format=b,file=heap.hprof <pid>`) and analyzing them with tools like Eclipse MAT or VisualVM.
Define a clear multi-step workflow: capture → load into analyzer → identify top memory consumers → detect leaks → validate fixes, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teach it, and replace with actionable content such as common heap dump patterns (memory leaks, large object retention, class histogram analysis).
Add references to detailed guides for advanced topics like GC root analysis, dominator trees, and OQL queries, structured as progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'heap dump analyzer' numerous times without providing any actual guidance, commands, or techniques for analyzing heap dumps. Every section restates the obvious rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no tool references (e.g., jmap, Eclipse MAT, VisualVM), no concrete steps for analyzing a heap dump. The skill describes itself rather than instructing. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for capturing, loading, or analyzing a heap dump, no validation checkpoints, and no error recovery guidance. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive placeholder with no meaningful structure. There are no references to detailed guides, no separation of quick-start vs. advanced content, and no navigation to related resources. | 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
3076d78
- 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.