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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill gc-log-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 actions, meaningful trigger terms, and explicit usage guidance. The only distinguishing element is the domain-specific name 'GC Log Analyzer', but this alone is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific capabilities like 'Parses Java/JVM garbage collection logs, identifies memory leaks, analyzes GC pause times, and detects heap pressure issues'
Include a 'Use when...' clause with natural trigger terms: 'Use when analyzing GC logs, investigating memory issues, JVM performance problems, heap dumps, or when users mention garbage collection, OutOfMemoryError, or GC pauses'
Remove the duplicate trigger term and expand with variations users would naturally say: 'garbage collection', 'GC pauses', 'memory leaks', 'JVM logs', 'heap analysis'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Gc Log Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'parse GC logs', 'identify memory leaks', or 'analyze pause times'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('gc log analyzer, gc log analyzer'). Missing natural user terms like 'garbage collection', 'memory analysis', 'JVM logs', 'heap', 'GC pauses', or '.log files'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'GC Log Analyzer' is somewhat specific to garbage collection analysis, which provides some distinctiveness. However, without concrete actions or clear triggers, it could still conflict with general log analysis or performance monitoring skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains zero actionable information about GC log analysis - no parsing techniques, no common GC patterns to identify, no tools or commands, and no examples of actual GC log entries or how to interpret them.
Suggestions
Add concrete code examples for parsing GC logs (e.g., regex patterns for G1GC, ZGC, or Parallel GC log formats)
Include specific commands for common GC log analysis tools (e.g., GCViewer, GCEasy, or command-line parsing with grep/awk)
Provide example GC log snippets with annotations showing how to identify memory leaks, long pauses, or allocation failures
Add a workflow with clear steps: collect logs -> parse -> identify patterns -> diagnose issues -> recommend tuning
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about GC log 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 GC logs. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for parsing GC logs, identifying issues, or interpreting results - just vague claims about 'step-by-step guidance' without any actual steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources. No references to GC log formats, analysis tools, or related documentation are provided. | 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.