thread-dump-analyzer
Thread Dump Analyzer - Auto-activating skill for Performance Testing. Triggers on: thread dump analyzer, thread dump analyzer Part of the Performance Testing skill category.
34
3%
Does it follow best practices?
Impact
89%
1.03xAverage 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/thread-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 title and category label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no explicit guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions such as 'Parses Java thread dumps to detect deadlocks, identify blocked threads, analyze thread states, and summarize contention hotspots.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user provides a thread dump, mentions jstack output, asks about deadlocks, blocked threads, thread contention, or needs to analyze JVM thread states.'
Remove the duplicated trigger term ('thread dump analyzer' is listed twice) and expand with varied natural phrases users might say, such as 'thread dump', 'stack trace', 'deadlock detection', 'jstack'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Thread Dump Analyzer', 'Performance Testing') but describes no concrete actions. There are no specific capabilities listed such as 'parse thread states', 'detect deadlocks', 'identify blocked threads', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is limited to a duplicated trigger phrase with no explicit 'Use when...' guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'thread dump analyzer' repeated twice. It misses natural user phrases like 'thread dump', 'deadlock', 'blocked threads', 'jstack', 'thread contention', 'stack trace analysis', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'thread 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 reduces 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 template with no substantive content. It contains zero actionable information about thread dump analysis — no code for parsing thread dumps, no patterns to look for (deadlocks, thread contention, blocked threads), no tool recommendations, and no workflow. It is entirely boilerplate that wastes tokens without teaching Claude anything.
Suggestions
Add concrete, executable examples showing how to capture and parse thread dumps (e.g., using jstack, jcmd, or programmatic approaches), with code for identifying deadlocks and high-contention threads.
Define a clear multi-step workflow: capture thread dump → parse/categorize threads by state → identify deadlocks → detect thread pools with contention → generate summary report, with validation at each step.
Include specific patterns to look for (BLOCKED threads, lock contention chains, runaway thread pools) with example thread dump snippets and expected analysis output.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities' descriptions) that provide no actionable information and replace with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'thread dump analyzer' excessively, and provides zero domain-specific information about actually analyzing thread dumps. | 1 / 3 |
Actionability | There are no concrete steps, commands, code examples, or specific guidance for analyzing thread dumps. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints — just generic claims about capabilities without any actual process described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or advanced guides, and no meaningful structure beyond boilerplate headings. | 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
4dee593
- 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.