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 extremely thin—it essentially just names the skill and its category without describing any concrete capabilities, use cases, or meaningful trigger terms. The trigger list is a duplicate of the same phrase, and there is no 'Use when...' clause. It would be nearly impossible for Claude to reliably select this skill based on user intent.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Parses Java heap dump files (.hprof), identifies memory leaks, analyzes object retention graphs, and reports dominant memory consumers.'
Add a 'Use when...' clause with natural trigger terms like 'memory leak', 'OutOfMemoryError', 'OOM', 'heap analysis', '.hprof file', 'memory profiling', 'GC issues'.
Remove the duplicate trigger term and expand coverage to include variations users would naturally say, such as 'analyze heap dump', 'debug memory usage', 'heap snapshot'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Heap Dump Analyzer', 'Performance Testing') but provides no concrete actions. It does not describe what the skill actually does—no mention of parsing heap dumps, identifying memory leaks, analyzing object retention, etc. | 1 / 3 |
Completeness | The 'what' is essentially absent—it only names itself without describing capabilities. The 'when' is limited to a redundant trigger phrase with no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'heap dump analyzer' repeated twice. It misses natural user phrases like 'memory leak', 'heap analysis', 'OutOfMemoryError', 'OOM', 'memory profiling', '.hprof', 'GC analysis', 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 vague 'Performance Testing' category label could overlap with other performance-related skills. The lack of specific actions weakens distinctiveness. | 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 placeholder that provides no actual content about heap dump analysis. It contains only boilerplate meta-descriptions of what the skill supposedly does without any concrete instructions, code, tools, or workflows. It would be entirely useless for guiding Claude to perform heap dump analysis.
Suggestions
Add concrete, executable examples using actual heap dump tools (e.g., jmap, Eclipse MAT, VisualVM) with specific commands like `jmap -dump:format=b,file=heap.hprof <pid>`.
Define a clear multi-step workflow: capture heap dump → open in analyzer → identify top memory consumers → detect leaks → generate report, with validation at each step.
Include specific patterns to look for in heap dumps (e.g., large object arrays, duplicate strings, classloader leaks) with example output interpretation.
Remove all the meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actionable technical content about heap dump analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'heap dump analyzer' excessively without providing any actual knowledge, commands, or techniques that Claude doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no tool references, no examples of how to actually analyze a heap dump. Every section is vague meta-description rather than instruction. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but includes none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
87f14eb
- 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.