analyzing-logs
Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".
57
50%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/log-analysis-tool/skills/analyzing-logs/SKILL.mdQuality
Discovery
100%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 is a well-crafted skill description that hits all the key criteria. It provides specific capabilities, natural trigger terms, explicit 'use when' guidance, and a clear niche. The description is concise yet comprehensive, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzing logs for performance insights, issue detection, slow requests, error patterns, and resource usage. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyze application logs for performance insights, slow requests, error patterns, resource usage) and 'when' (troubleshooting performance issues, debugging errors) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'analyze logs', 'find slow requests', 'detect error patterns', 'troubleshooting performance issues', 'debugging errors'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to application log analysis for performance and error detection. The specific domain (logs, slow requests, error patterns, resource usage) creates a distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 almost entirely descriptive rather than instructive. It explains what log analysis is and what the skill would do in abstract terms, but provides zero executable code, commands, regex patterns, or concrete examples. The content is heavily padded with sections that repeat similar information and explain concepts Claude already understands, while failing to deliver the actionable guidance needed to actually perform log analysis.
Suggestions
Replace abstract descriptions with concrete, executable examples: provide actual grep/awk/sed commands for extracting slow requests (e.g., `grep -E 'duration=[0-9]{4,}' app.log | sort -t= -k2 -n`), regex patterns for common error formats, and Python scripts for log parsing.
Remove redundant sections (Overview, How It Works, When to Use) and consolidate into a lean skill that assumes Claude knows what log analysis is — focus only on the specific patterns, thresholds, and commands to use.
Add concrete validation steps: specify what constitutes a 'slow request' (e.g., >500ms threshold), provide example log line formats the skill expects, and include sample output showing what the analysis report should look like.
Either create bundle files with reusable scripts/templates for log parsing and reference them, or remove the 'Resources' section that lists generic topics with no actual links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use This Skill', and 'Integration' are padded with unnecessary context that doesn't add actionable value. The skill explains what log analysis is rather than instructing how to do it. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. The 'Examples' section describes what the skill 'will do' in abstract terms rather than providing actual grep/awk commands, regex patterns, or scripts. The 'Instructions' section is a vague numbered list with no specifics on how to actually perform any step. | 1 / 3 |
Workflow Clarity | Steps are listed but entirely abstract with no validation checkpoints. There are no specific commands, thresholds, or concrete criteria for identifying slow requests or error patterns. The error handling section lists things to check but provides no actual diagnostic commands or feedback loops. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files to support it. Content is poorly organized with redundant sections (Overview, How It Works, When to Use, Instructions all overlap significantly). The 'Resources' section lists generic topic names with no actual links or file references. | 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
3a2d27d
- 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.