CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

error-detective

Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use when debugging issues, analyzing logs, or investigating production errors.

Quality

69%

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 ./skills/error-detective/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Weight 40%Scale 1-5

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

The body is a thin, templated skeleton: well-structured and short, but padded with generic 'use when / do not use when / instructions' boilerplate and lacking any concrete artifacts (regexes, log queries, worked examples) that would make an error-detective skill executable. The 5-step approach is a sensible sequence yet has no validation checkpoints.

Suggestions

Replace the generic 'Use this skill when', 'Do not use this skill when', and 'Instructions' sections with domain-specific content or delete them — they restate the frontmatter and consume tokens without adding guidance.

Add concrete executable material: example regex patterns for error extraction, sample Elasticsearch/Splunk aggregation queries, and a worked stack-trace correlation case.

Insert validation checkpoints into the Approach workflow, e.g., 'verify the root-cause hypothesis against the correlated deployment timeline before proposing a fix' and a retry loop when evidence is inconclusive.

DimensionReasoningScore

Conciseness

Roughly 40% of the body is content-free boilerplate — 'Working on error detective tasks or workflows', 'The task is unrelated to error detective', 'Clarify goals, constraints, and required inputs' — that adds no information beyond the frontmatter and assumes no intelligence. Although the Focus Areas/Approach/Output lists are lean, several padded sections make it noticeably verbose per anchor 2, above anchor 1 only because no known concepts are re-explained.

2 / 5

Actionability

Guidance stays at the hint level — 'Start with error symptoms, work backward to cause', 'Look for patterns across time windows' — with zero concrete artifacts: no example regex for error extraction, no sample Elasticsearch/Splunk queries, no commands or code. This matches anchor 2 ('high-level hints but missing the specific steps to execute'); it is above anchor 1 because the Approach and Output sections do give real directional structure.

2 / 5

Workflow Clarity

The Approach section lists a coherent 5-step sequence (symptoms → time-window patterns → deployment correlation → cascading failures → rate spikes), but no validation or verification checkpoints exist anywhere — e.g., no step confirming a root-cause hypothesis against evidence. This fits anchor 3 ('sequence present but checkpoints missing or implicit') and is below anchor 4, which requires most checkpoints present.

3 / 5

Progressive Disclosure

The body is under 50 lines, single-purpose, and organized into clear sections (Focus Areas, Approach, Output) with no nested or buried references, matching the simple-skill exception where well-organized sections alone earn a 5. No bundle files exist to verify, and none are structurally required at this size; it does not fit anchor 4's 'minor organization gaps' since nothing is misplaced across files.

5 / 5

Total

12

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 description: third-person voice, concrete multi-action capability statement, and an explicit 'Use when...' clause with natural trigger phrases. It is comprehensive on what/when, with only minor gaps in keyword synonyms and some trigger breadth that could overlap general debugging skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Search logs and codebases for error patterns, stack traces, and anomalies', 'Correlates errors across systems and identifies root causes' — but has minor coverage gaps (e.g., monitoring for recurrence and timeline construction from the body are absent). Not fully comprehensive, so it fits anchor 4 better than 5.

4 / 5

Completeness

Explicitly answers both questions: what ('Search logs and codebases for error patterns... Correlates errors across systems and identifies root causes') and when ('Use when debugging issues, analyzing logs, or investigating production errors') with concrete trigger phrases. This matches the anchor-5 example pattern and exceeds anchor 4, whose 'when' clause is less specific.

5 / 5

Trigger Term Quality

Natural user phrases like 'debugging issues', 'analyzing logs', 'investigating production errors', and 'stack traces' are present, matching anchor 4's 'good keyword coverage; a few natural terms missing'. Common variations such as 'troubleshooting', 'exceptions', or 'crashes' are absent, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The log-analysis/root-cause niche is mostly distinct, but 'debugging issues' is a broad trigger with minor overlap risk against general debugging and code-review skills. Fits anchor 4 ('mostly distinct; minor overlap risk') rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/error-detective/SKILL.md

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.