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
Quality
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 placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe any concrete capabilities, lacks meaningful trigger terms, and provides no guidance on when Claude should select this skill. The repeated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes Java thread dumps to identify deadlocks, blocked threads, and resource contention issues'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user shares a thread dump, mentions jstack output, asks about deadlocks, or needs help diagnosing thread-related performance issues'
Add varied trigger terms users would naturally say: 'thread dump', 'jstack', 'deadlock', 'blocked threads', 'stack trace analysis', 'thread contention'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Thread Dump Analyzer') without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'analyze', 'identify deadlocks', 'detect blocked threads', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' guidance is just a redundant trigger phrase. There's no explicit 'Use when...' clause explaining scenarios for activation. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'thread dump analyzer' repeated twice, which is redundant and overly narrow. Missing natural variations users would say like 'thread dump', 'analyze threads', 'deadlock', 'blocked threads', 'stack trace', 'jstack output'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'thread dump' is fairly specific to JVM/performance analysis domain, which provides some distinctiveness. However, the lack of detail about what it does could cause confusion with other performance testing 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 content is essentially a placeholder template with no actual instructional value. It contains no concrete guidance on thread dump analysis - no code for parsing dumps, no patterns for identifying deadlocks or contention, no tool recommendations, and no examples. The content describes what a skill should do rather than teaching Claude how to analyze thread dumps.
Suggestions
Add concrete code examples for parsing thread dumps (e.g., using jstack output, parsing with regex or dedicated libraries)
Include specific patterns to identify: deadlocks, thread contention, blocked threads, and runaway threads with example stack traces
Provide a clear workflow: 1) Capture dump 2) Parse threads 3) Identify blocked/waiting states 4) Find lock holders 5) Report findings
Add tool-specific guidance (jstack, VisualVM, thread dump analyzers) with executable commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about thread dump analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for analyzing thread dumps. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Thread dump analysis involves specific steps (capturing dumps, identifying blocked threads, finding deadlocks, analyzing stack traces) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual learning. No references to detailed materials, no examples, no organized sections with real 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
0c08951
- 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.