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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill heap-dump-analyzer

What are skills?

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what the skill actually does, lists redundant trigger terms, and lacks any guidance on when Claude should select it. The only redeeming quality is that 'heap dump' is a reasonably specific technical domain.

Suggestions

Add specific capabilities the skill performs, e.g., 'Analyzes Java heap dumps to identify memory leaks, find large objects, detect class loader issues, and generate memory usage reports'

Add a 'Use when...' clause with natural trigger terms like 'Use when analyzing .hprof files, investigating OutOfMemoryErrors, memory leaks, heap analysis, or JVM memory issues'

Expand trigger terms to include variations users would naturally say: 'memory dump', 'OOM error', '.hprof', 'memory leak', 'heap analysis', 'JVM memory'

Dimension	Reasoning	Score
Specificity	The description only names the tool ('Heap Dump Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'analyze memory leaks', 'identify object retention', or 'generate memory reports'.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond naming itself, and has no explicit 'Use when...' clause. The 'Triggers on' section is not a proper when-to-use guidance and only repeats the skill name.	1 / 3
Trigger Term Quality	The trigger terms are redundant ('heap dump analyzer' listed twice) and miss natural variations users might say like 'memory analysis', 'OOM', 'out of memory', 'memory leak', '.hprof files', or 'heap analysis'.	1 / 3
Distinctiveness Conflict Risk	While 'heap dump' is a fairly specific technical domain, the lack of concrete actions and the generic 'Performance Testing' category could cause overlap with other performance-related skills. The term is specific enough to avoid major conflicts.	2 / 3
	Total	5 / 12 Passed

Implementation

This skill is an empty template with no actual content about heap dump analysis. It contains only generic boilerplate text that could apply to any skill topic. There is no actionable guidance, no code examples, no tool recommendations (like Eclipse MAT, VisualVM, jhat), and no explanation of heap dump analysis concepts or workflows.

Suggestions

Add concrete code/commands for acquiring heap dumps (e.g., `jmap -dump:format=b,file=heap.hprof <pid>` or JVM flags like `-XX:+HeapDumpOnOutOfMemoryError`)

Include step-by-step workflow for analyzing dumps: load into tool → identify largest objects → analyze dominator tree → find GC roots → identify leak suspects

Provide specific tool guidance for Eclipse MAT or VisualVM with example queries like OQL for finding memory leaks

Add examples of common memory leak patterns and how to identify them in heap dumps (e.g., growing collections, unclosed resources, static field accumulation)

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about heap dump analysis.	1 / 3
Actionability	Contains zero concrete guidance - no code, no commands, no specific steps for analyzing heap dumps. The entire content describes what the skill supposedly does rather than instructing how to do anything.	1 / 3
Workflow Clarity	No workflow is provided whatsoever. Heap dump analysis involves specific steps (acquiring dumps, loading into tools like MAT/VisualVM, identifying memory leaks, analyzing dominator trees) - none of which are mentioned.	1 / 3
Progressive Disclosure	No structure beyond generic headings. No references to detailed materials, no examples, no links to tool documentation or analysis techniques. The content is a hollow template with no actual substance to organize.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Reviewed

21 days ago

Table of Contents

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