CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/log-analysis-tool/skills/analyzing-logs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-organized and readable but overly descriptive and conceptual, lacking executable code, integrated validation, and explicit pointers to the bundled scripts. It reads more like a product overview than an actionable, token-efficient skill body.

Suggestions

Replace conceptual Overview/Best Practices prose with executable examples (e.g., grep/awk commands to find slow requests and group errors) and reference the bundled scripts by path.

Add explicit validation checkpoints to the Instructions workflow (e.g., verify parsed timestamp format, confirm no log lines were dropped before generating the report).

Link the existing bundle files (scripts/analyze_log_file.py, scripts/aggregate_logs.py) from the body so progressive disclosure is clearly signaled rather than leaving the scripts orphaned.

DimensionReasoningScore

Conciseness

Sections like Overview, How It Works, and Best Practices restate concepts Claude already knows (what log analysis is, structured logging, log rotation) and could be trimmed; it is mostly efficient but padded with unnecessary explanation.

2 / 3

Actionability

The Instructions and Examples describe steps at a high level ('Apply pattern matching', 'Extract relevant data') rather than giving executable commands, though prerequisite tools (grep, awk, sed) and a log directory path provide partial concreteness.

2 / 3

Workflow Clarity

A numbered sequence exists in Instructions, but there are no explicit validation checkpoints or feedback loops, and the Error Handling section is a generic checklist rather than integrated recovery steps.

2 / 3

Progressive Disclosure

The body is a monolithic overview with bundle scripts (aggregate_logs.py, analyze_log_file.py) present but never referenced or linked from the SKILL.md, so structure exists but navigation/signaling to the bundle is missing.

2 / 3

Total

8

/

12

Passed

Description

92%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with concrete capabilities and natural triggers covering both what and when. Slight genericness in the trigger phrasing keeps it from being fully conflict-proof against general debugging skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'slow requests, error patterns, and resource usage'—mirroring the score-3 anchor of enumerating specific capabilities.

3 / 3

Completeness

Clearly answers both what (log analysis for slow requests/errors/resource usage) and when via an explicit 'Use when troubleshooting performance issues or debugging errors' trigger clause.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases ('analyze logs', 'find slow requests', 'detect error patterns') are plausible user utterances with good coverage of the skill's scope.

3 / 3

Distinctiveness Conflict Risk

The log-analysis niche is reasonably distinct, but trigger terms like 'analyze logs' are generic enough to overlap with general debugging/troubleshooting skills, so not a clean score-3 niche.

2 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.