CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

runtime-error-explainer

Explains runtime errors and compilation failures with actionable debugging guidance. Use when Python or Java code throws runtime exceptions (NullPointerException, TypeError, AttributeError, etc.), compilation errors (syntax errors, type mismatches, import failures), or dependency issues. Analyzes error messages, stack traces, and code context to identify root causes and provide concrete fixes with examples. Distinct from test-related errors - focuses on errors during normal code execution and build processes.

Quality

78%

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

Quality

Content

56%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 delivers a clear, actionable workflow and concrete executable examples, but pays for it with severe token bloat: the Common Error Patterns section duplicates both the bundled error_catalog.md and knowledge Claude already has. Moving that section into the existing catalog reference would fix both the conciseness and progressive-disclosure weaknesses at once.

Suggestions

Move the ~500-line 'Common Error Patterns' section out of SKILL.md and into references/error_catalog.md (which already covers the same errors), keeping only one short worked example inline to illustrate the explanation template.

Fix the minor code inaccuracies: the NPE Solution 1 snippet should declare "String name" once before the if/else, and the "python -v script.py" comment should be removed or corrected since -v traces imports rather than error output.

Add an explicit feedback loop after verification (e.g., 'If verification fails, re-read the stack trace from the top frame down and repeat Steps 3-5') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The ~500-line 'Common Error Patterns' section extensively explains fixes Claude already knows ("Python requires colon to start code blocks", adding null checks, "String result = String.valueOf(42)") and duplicates content in references/error_catalog.md. It is not 1 because the workflow, explanation template, and language-specific notes are genuinely useful non-padding content; it is not 3 because more than half the body is redundant with Claude's existing knowledge and with the bundled catalog.

2 / 5

Actionability

Mostly executable guidance with concrete before/after code and specific commands ("python -m py_compile script.py", "javac -d bin src/com/example/MyClass.java", "java -cp bin com.example.MyClass"). It is not 5 due to minor gaps: the NPE Solution 1 snippet declares "String name" separately inside the if and else branches (unusable afterward), and "python -v script.py" is mischaracterized as producing 'more verbose error output'; it is well above 3 because nearly all examples are complete and runnable.

4 / 5

Workflow Clarity

A clear six-step sequence (Gather Context → Categorize → Extract → Root Cause → Explain → Next Steps) with verification checkpoints in the template ("## Verification [How to verify the fix works]") and per-error verification commands. It is not 5 because there is no explicit feedback loop for when verification fails (recovery guidance is only loosely covered in Step 6); it is not 3 because explicit verification steps are present, not merely implied.

4 / 5

Progressive Disclosure

Both referenced files (references/error_catalog.md, references/debugging_guide.md) exist, are one level deep, and are clearly signaled in the Resources section and in Steps 2 and 4. It is not 4 because roughly 500 lines of worked error explanations are inlined in the body, duplicating the error catalog — a major 'content that should be separate is inline' gap rather than a minor organization issue.

3 / 5

Total

13

/

20

Passed

Description

92%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: third-person voice, concrete actions, an explicit 'Use when...' trigger clause with named exception types, and an explicit boundary statement against test-related error skills. The only gap is a few missing natural trigger synonyms (e.g., 'crash', 'build failure').

DimensionReasoningScore

Specificity

Quotes multiple concrete third-person actions: "Explains runtime errors and compilation failures", "Analyzes error messages, stack traces, and code context to identify root causes", "provide concrete fixes with examples" — comprehensive coverage of what the skill does. It is not 4 because the action list has no meaningful gaps within its domain; it is not below 5 since every stated action is specific rather than generic.

5 / 5

Completeness

Explicitly answers both: what ("Analyzes error messages, stack traces, and code context to identify root causes and provide concrete fixes with examples") and when ("Use when Python or Java code throws runtime exceptions..., compilation errors..., or dependency issues") with concrete trigger phrases. It is not 4 because the when-clause is fully explicit and enumerates specific error types rather than being merely adequate.

5 / 5

Trigger Term Quality

Includes many natural terms users would paste or say: "NullPointerException, TypeError, AttributeError", "syntax errors, type mismatches, import failures", "dependency issues", "stack traces". It is not 5 because common phrasings like "crash", "build failure", or "help me debug this error" are absent; it is not 3 because coverage clearly goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (runtime/compilation errors in Python and Java) and explicitly demarcates boundaries: "Distinct from test-related errors - focuses on errors during normal code execution and build processes". It is not 4 because it actively distinguishes itself from the closest overlapping skill category rather than leaving only minor overlap risk.

5 / 5

Total

19

/

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

skill_md_line_count

SKILL.md is long (850 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

ArabelaTso/Skills-4-SE

Path

skills/runtime-error-explainer/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.