CtrlK
BlogDocsLog inGet started
Tessl Logo

error-detective

Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.

49

Quality

54%

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/AI-Agents-Safe-Coding-Skills-claude/skills/error-detective/SKILL.md

The canonical home for this skill is error-detective in administrakt0r/AI-Agents-Safe-Coding-Skills

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 content is well-structured but largely abstract: it describes an error-detection approach without providing the concrete regex patterns, queries, or commands it advertises, and it points to a reference file that is missing from the bundle.

Suggestions

Add concrete, executable artifacts the Output section promises — example regex patterns for common error/stack-trace formats and sample Elasticsearch/Splunk queries — to lift actionability above generic hints.

Fix or remove the dangling reference to "resources/implementation-playbook.md"; either create the file under references/ or inline the playbook content so navigation is not broken.

Replace the generic Instruction bullets ("Clarify goals...", "Apply relevant best practices...") with error-detection-specific guidance, and add a validation step to the Approach workflow (e.g., confirm a root-cause hypothesis against the evidence before reporting).

DimensionReasoningScore

Conciseness

The body is mostly efficient bullet points, but generic filler such as "Clarify goals, constraints, and required inputs" and "Apply relevant best practices and validate outcomes" plus the boilerplate "You are an error detective..." line could be tightened, fitting score 3 rather than the lean score-4 anchor.

3 / 5

Actionability

It offers high-level hints ("Start with error symptoms, work backward to cause", "Look for patterns across time windows") and names tools like Elasticsearch/Splunk but gives no actual regex patterns, queries, or commands despite promising them in the Output section, matching the minimal-guidance score-2 anchor.

2 / 5

Workflow Clarity

The Approach section provides a coherent 5-step sequence, but there are no validation checkpoints or feedback loops for verifying a root-cause hypothesis, fitting score 3 rather than the checkpoint-rich score-4 anchor.

3 / 5

Progressive Disclosure

Sections are reasonably organized for a short single-domain skill, but it references "resources/implementation-playbook.md" which does not exist in the bundle, making the reference a dangling pointer that weakens navigation and caps it at score 3.

3 / 5

Total

11

/

20

Passed

Description

66%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.

The description is specific and mostly distinctive with good trigger terms, but it omits any explicit "when to use" guidance, which the rubric penalizes by capping completeness at 3.

DimensionReasoningScore

Specificity

Names the error-detection domain and lists several concrete actions — "Search logs and codebases for error patterns, stack traces, and anomalies", "Correlates errors across systems", "identifies root causes" — with only minor coverage gaps, fitting the score-4 anchor rather than the comprehensive score-5 example.

4 / 5

Completeness

It clearly answers "what" the skill does but provides no "Use when..." clause, so per the rubric a missing explicit trigger caps completeness at 3, below the score-4 anchor that requires both what and when.

3 / 5

Trigger Term Quality

Includes natural user-facing terms like "error patterns", "stack traces", and "logs", giving good keyword coverage, but misses common synonyms/extensions (debug, troubleshoot, crash) so it falls short of the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The error/root-cause niche is mostly distinct from other skills, though "search logs and codebases" is broad enough to risk minor overlap with general debugging tools, matching score 4 rather than the clearly-niched score 5.

4 / 5

Total

15

/

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.

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
administrakt0r/AI-Agents-Safe-Coding-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.