CtrlK
BlogDocsLog inGet started
Tessl Logo

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or get distribution stats.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tightly-structured, action-oriented skill body: executable command, full parameter reference, concrete examples, and a representative output sample. Sections are well organized and the only reference (the analyze_logs.py script) is one level deep and present in the bundle.

DimensionReasoningScore

Conciseness

The body is lean — it assumes competence, omits explanations of log concepts, and every section (formats, parameters, examples, output sample) earns its place; the illustrative output block justifies its length by showing expected formatting.

3 / 3

Actionability

Provides an executable invocation, a complete parameter table with defaults, and four copy-paste-ready example commands with real flags, matching the fully-executable anchor.

3 / 3

Workflow Clarity

A single-action skill (run the script) whose action is unambiguous; the operation is read-only so no validation feedback loop is required, and per the simple-skill note clarity scores 3.

3 / 3

Progressive Disclosure

Well-organized overview sections (Features, Formats, Usage, Parameters, Examples, Output) with a single one-level-deep reference to the bundled scripts/analyze_logs.py; the file exists in the bundle.

3 / 3

Total

12

/

12

Passed

Description

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.

A strong, third-person description that concretely states capabilities, supported formats, and explicit usage triggers with natural phrasing. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'troubleshoot errors', 'identify peak error periods', 'produce error clustering, frequency statistics, and time distribution reports' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers what (analyze log files, supported formats, report types) AND when ('Use when a user uploads a .log file and asks to analyze errors...'), the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Natural user phrasing is well covered: 'analyze errors', 'find patterns', 'debug issues', 'get distribution stats', plus the '.log file' cue, matching good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

A clear log-error-analysis niche with format-specific detection and distinct '.log file / analyze errors' triggers makes collision with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
zebbern/claude-code-guide
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.