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 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 guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add concrete actions the skill performs, e.g., 'Parses GC log files, identifies long pause times, detects memory leaks, and summarizes heap usage patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about garbage collection logs, GC pauses, JVM memory issues, heap analysis, or .gc.log files.'
Remove the duplicate trigger term ('gc log analyzer' is listed twice) and expand with varied natural phrases users might say, such as 'GC tuning', 'garbage collection performance', 'JVM GC analysis'.
| 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 just a redundant trigger phrase rather than meaningful usage guidance. There is no explicit 'Use when...' clause. | 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', '.log files', 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 specific actions and the broad 'Performance Testing' category label could cause overlap with other performance-related 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 is an empty template with no actual content about GC log analysis. It contains only boilerplate placeholder text that describes what a skill would do without providing any actionable guidance, code, commands, or domain-specific knowledge about parsing, interpreting, or analyzing garbage collection logs.
Suggestions
Add concrete, executable examples of parsing GC logs (e.g., using tools like GCViewer, gceasy.io, or command-line parsing with grep/awk patterns for common GC log formats like G1GC, ZGC, etc.)
Include a clear workflow: 1) Identify GC log format, 2) Parse with specific tool/command, 3) Identify key metrics (pause times, throughput, heap usage), 4) Diagnose common issues (long pauses, memory leaks, premature promotion)
Add specific code examples for extracting and analyzing GC metrics, such as Python scripts or shell commands that process GC log files and produce actionable summaries
Replace all boilerplate sections (When to Use, Capabilities, Example Triggers) with actual domain knowledge about GC log patterns, JVM flags for enabling GC logging, and interpretation guidelines for different collectors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance on GC log analysis. Every section restates the same vague concept. | 1 / 3 |
Actionability | There are zero concrete instructions, commands, code examples, or specific guidance. The content describes rather than instructs, with no executable steps for analyzing GC logs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims about providing 'step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to detailed materials, no links to examples or advanced guides, and no meaningful structure beyond generic 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
87f14eb
- 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.