gc-log-analyzer
Gc Log Analyzer - Auto-activating skill for Performance Testing. Triggers on: gc log analyzer, gc log analyzer Part of the Performance Testing skill category.
60
3%
Does it follow best practices?
Impact
100%
1.01xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/gc-log-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 names the skill and its category but provides no substantive information about what it does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Parses GC log files, identifies long pause times, detects memory leaks, and generates heap utilization reports.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user mentions GC logs, garbage collection analysis, JVM memory issues, heap usage, GC pause times, or .gc.log files.'
Remove the duplicate trigger term ('gc log analyzer' is listed twice) and expand with common variations users would naturally use such as 'garbage collection', 'GC pauses', 'JVM tuning', 'memory pressure'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('GC Log Analyzer', 'Performance Testing') but describes no concrete actions. There is no mention of what the skill actually does—no verbs like 'parse', 'analyze', 'detect pauses', 'generate reports', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'gc log analyzer' repeated twice. It misses natural variations users would say such as 'garbage collection', 'GC logs', 'heap analysis', 'GC pause times', 'JVM memory', '.gc.log', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'GC Log Analyzer' is fairly niche and unlikely to conflict with many other skills, but the lack of specificity about what it does versus other performance testing skills creates some overlap risk within that category. | 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 shell with no substantive content about GC log analysis. It consists entirely of generic boilerplate text that could apply to any skill topic — there are no concrete instructions, code examples, tool references, or workflows specific to GC log analysis or performance testing. It provides zero value to Claude beyond what the skill's title alone would convey.
Suggestions
Add concrete, executable examples of parsing GC logs (e.g., regex patterns for G1GC/ZGC log formats, or commands using tools like GCViewer or GCEasy CLI)
Define a clear workflow: 1) Enable GC logging with specific JVM flags, 2) Collect logs, 3) Parse key metrics (pause times, heap usage, promotion rates), 4) Identify common issues (long pauses, memory leaks, premature promotion), 5) Validate findings
Include specific code snippets for extracting and summarizing GC metrics (e.g., Python script to parse GC pause times, or shell commands to grep for Full GC events)
Replace the generic 'Capabilities' and 'Example Triggers' sections with actual reference content about GC log formats, common JVM flags (-Xlog:gc*, -XX:+PrintGCDetails), and diagnostic patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actual information. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty platitudes. It explains what triggers the skill rather than providing any substantive content about GC log analysis. | 1 / 3 |
Actionability | There is zero actionable content — no code, no commands, no concrete steps for analyzing GC logs. No mention of specific GC log formats (G1, ZGC, Shenandoah), parsing techniques, tools (GCViewer, GCEasy), or metrics to extract. The skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. GC log analysis involves multi-step processes (collecting logs, parsing, identifying patterns, diagnosing issues) but none of these steps are outlined. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic boilerplate with no references to supporting files, no structured sections with real content, and no bundle files to support it. There is nothing to progressively disclose because there is no substantive 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
22f797a
- 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.