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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill thread-dump-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete capabilities, meaningful trigger terms, and explicit usage guidance. The only distinguishing element is the domain-specific term 'thread dump' which provides minimal differentiation.
Suggestions
Add specific capabilities: 'Analyzes Java thread dumps to identify deadlocks, blocked threads, thread contention, and resource bottlenecks'
Expand trigger terms to include natural variations: 'jstack output', 'stack trace analysis', 'deadlock detection', 'thread states', 'blocked threads', '.tdump files'
Add explicit 'Use when...' clause: 'Use when the user shares thread dump output, asks about deadlocks, needs to analyze JVM thread states, or troubleshoot application hangs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Thread Dump Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'analyze deadlocks', 'identify blocked threads', or 'detect thread contention'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is circular (use thread dump analyzer when you say 'thread dump analyzer'). No explicit trigger guidance or use cases are provided. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('thread dump analyzer' listed twice) and miss natural variations users would say like 'thread dump', 'stack trace', 'deadlock', 'blocked threads', 'jstack output', or 'thread analysis'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'thread dump' is fairly specific to Java/JVM performance analysis, which provides some distinctiveness. However, the vague description could still overlap with general 'performance testing' or 'log analysis' skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 examples of common thread states or stack trace interpretation. The content tells Claude what the skill supposedly does rather than teaching how to do it.
Suggestions
Add concrete code examples for parsing thread dumps (e.g., using jstack output, parsing thread states, identifying BLOCKED/WAITING threads)
Include specific patterns to look for: deadlock detection, thread pool exhaustion, lock contention with example stack traces
Provide a clear workflow: 1) Capture dump 2) Parse thread states 3) Identify blocked threads 4) Trace lock holders 5) Report findings
Add example input (sample thread dump snippet) and expected output (analysis summary) to make the skill actionable
| 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 actual steps for analyzing thread dumps. The content describes what the skill supposedly does but never instructs 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
69%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
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.