error-explanation-generator

Explains test failures and provides actionable debugging guidance. Use when tests fail (unit, integration, E2E), builds fail, or code throws errors. Analyzes error messages, stack traces, and test output to identify root causes and suggest concrete fixes. Handles pytest, jest, junit, mocha, vitest, selenium, cypress, playwright, and other testing frameworks across Python, JavaScript/TypeScript, Java, Go, and other languages.

1.25x

Quality

79%

Does it follow best practices?

Impact

88%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/error-explanation-generator/SKILL.md

Quality

Content

67%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 with a clear workflow, executable commands, and genuinely useful reference files, but it is padded with worked examples and explanations of basic concepts Claude already knows. Trimming the inline examples and pushing detail into the existing references would improve token efficiency and progressive disclosure.

Suggestions

Reduce conciseness overhead by moving the four full worked examples (Assertion/TypeError/Timeout/Mock) into references/error_patterns.md and keeping only one compact illustration plus a pointer in SKILL.md.

Delete explanations of concepts Claude already knows (e.g., what AssertionError means, why Python 3 '/' returns floats, how to add null checks) and retain only the non-obvious diagnosis guidance.

Add an explicit validation feedback loop to the workflow (e.g., after generating a fix, run the suggested test command and only conclude once it passes) to lift workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but includes substantial unnecessary explanation of concepts Claude already knows (e.g., what AssertionError/TypeError mean, how to add null checks, why integer division returns floats) across four lengthy worked examples, fitting the 'mostly efficient but could be tightened' anchor at 3 rather than the minor-trim 4.	3 / 5
Actionability	Provides concrete executable commands ('pytest -v --tb=long', 'npm test -- --verbose', 'go test -v'), a structured output template, and before/after code fixes covering common cases, with only minor gaps from template placeholders.	4 / 5
Workflow Clarity	A clear six-step sequence (Gather -> Parse -> Extract -> Identify -> Provide -> Suggest Next Steps) with a Verification section in the template, but verification is framed as output for the user rather than an explicit validate-fix-retry feedback loop in Claude's own process, so it falls short of the 5 anchor.	4 / 5
Progressive Disclosure	References real one-level-deep files (references/error_patterns.md, references/debugging_strategies.md) clearly signaled in a Resources section, but substantial content that could live in those references (the four full worked examples and Framework-Specific Notes) is inlined in SKILL.md, keeping it below the cleanly-split 5.	4 / 5
	Total	15 / 20 Passed

Description

91%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 strong: it clearly states what the skill does, provides explicit 'Use when' triggers with natural user phrasing, and enumerates supported frameworks to reduce ambiguity. Minor specificity gap keeps it just short of a perfect score.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Explains test failures and provides actionable debugging guidance', 'Analyzes error messages, stack traces, and test output to identify root causes and suggest concrete fixes') with only minor gaps, fitting the 'several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	Explicitly answers both what ('Explains test failures... Analyzes error messages, stack traces... identify root causes and suggest concrete fixes') and when ('Use when tests fail..., builds fail, or code throws errors') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Covers natural phrases users say ('Use when tests fail (unit, integration, E2E), builds fail, or code throws errors') plus extensive framework synonyms (pytest, jest, junit, mocha, vitest, selenium, cypress, playwright), matching the comprehensive-synonyms anchor at 5.	5 / 5
Distinctiveness Conflict Risk	Clear niche in test/build failure debugging with a specific trigger set and many named frameworks, giving only minor overlap risk with general debugging skills; not quite the minimal-conflict 5.	4 / 5
	Total	18 / 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
skill_md_line_count	SKILL.md is long (606 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/error-explanation-generator/SKILL.md
Commit: 4f38503

Reviewed: 8 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.