Name: error-detective
Rating: 49.6 (1 reviews)
Author: administrakt0r

error-detective

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

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/error-detective/SKILL.md

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

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 skill is a brief, well-sectioned overview with a clear diagnostic workflow, but it is almost entirely descriptive — no executable regex, queries, or commands — and its only progressive-disclosure reference is a broken path.

Suggestions

Add at least one executable example per focus area, e.g. a sample regex for stack-trace extraction and an Elasticsearch/Splunk query for error-rate spikes.

Replace generic "Instructions" bullets with concrete first steps, and drop the tautological "Use/Do not use this skill when" boilerplate.

Fix or remove the dangling `resources/implementation-playbook.md` reference — either create the file under `references/` and correct the path, or inline the few needed examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the templated "Use this skill when / Do not use this skill when" bullets and generic "Instructions" lines ("Apply relevant best practices and validate outcomes") are tautological filler that could be trimmed, matching the "mostly efficient but some unnecessary explanation" anchor.	3 / 5
Actionability	It names tools and outputs ("Log aggregation queries (Elasticsearch, Splunk)," "Regex patterns for error extraction") but provides no executable code, example regex, or sample query — high-level hints missing the specific steps to execute, matching the 2 anchor.	2 / 5
Workflow Clarity	The "Approach" section gives a clear five-step sequence, but there are no validation checkpoints or feedback loops; this is read-only analysis so the destructive-cap does not apply, landing on the "steps listed but checkpoints missing" anchor.	3 / 5
Progressive Disclosure	Sections are reasonably organized for a short skill, but the sole external reference — "open `resources/implementation-playbook.md`" — points to a non-existent path (no `resources/` or `references/` directory exists), so the reference is present but broken and poorly signaled.	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 states concrete capabilities clearly but omits any explicit "when to use" trigger guidance, which caps completeness. Trigger-term coverage is good but lacks common synonyms.

Suggestions

Append an explicit trigger clause, e.g. "Use when debugging errors, investigating stack traces, or finding root causes in logs or codebases."

Add natural synonyms users say, such as "debug," "exceptions," "crash," and "traceback," to broaden trigger-term coverage.

Tighten the niche by mentioning specific log sources or formats (e.g. "application logs," "production errors") to reduce overlap with general debugging skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Search logs and codebases for error patterns, stack traces, and anomalies," "Correlates errors across systems," "identifies root causes" — matching the "several specific actions; minor gaps" anchor rather than the fully comprehensive 5.	4 / 5
Completeness	The "what" is clear and specific, but there is no "Use when..." clause or equivalent explicit trigger guidance; the rubric caps completeness at 3 in that case.	3 / 5
Trigger Term Quality	Good natural coverage with "logs," "stack traces," "anomalies," "root causes," but misses common synonyms a user might say such as "debug," "exceptions," "crash," or "traceback," so it sits below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The log-analysis / root-cause niche is fairly distinct, with only minor overlap risk against generic debugging skills, matching the "mostly distinct" anchor rather than the clearly-niched 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/error-detective/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.