CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

error-handling

Validate error handling completeness across languages

Quality

68%

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

Quality

Content

71%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, concise, and highly actionable with concrete commands and a strict output schema, plus clear workflow sequencing and scope boundaries. The main weakness is progressive disclosure: the referenced language pattern files are not present in the bundle, which undermines the file-splitting strategy.

Suggestions

Ship the referenced languages/go.md, languages/python.md, and languages/typescript.md files, or inline the HARD/SHOULD/WARN patterns into the body if the files are not bundled.

Consolidate the duplicate scope statements between the Scope Declaration and Step 4's cross-validator boundaries to tighten conciseness.

Make the LSP step's optional status and the text-matching fallback more visually compact so the core detection flow reads as the primary path.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining basic concepts; the only mild redundancy is the scope being restated in Step 4's cross-validator boundaries, which could be trimmed.

4 / 5

Actionability

It provides concrete, executable bash commands, a precise JSON output schema, and explicit file-loading instructions; minor gaps are the LSP step being conditional and the referenced language files being absent from the bundle.

4 / 5

Workflow Clarity

The five steps are clearly sequenced with batching logic, intra-rule precedence, and an explicit LSP fallback; as a read-only analysis task it lacks destructive-operation validation, but its feedback logic via severity downgrades is solid.

4 / 5

Progressive Disclosure

It signals one-level-deep references to languages/go.md, python.md, and typescript.md, but those files do not exist in the bundle, so the disclosed structure is partly illusory and navigation would break.

3 / 5

Total

15

/

20

Passed

Description

53%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 clear and appropriately scoped but terse: it states what the skill does without enumerating concrete actions or providing any "Use when" trigger guidance. Adding trigger phrases and listing the violation categories it detects would lift several dimensions.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when reviewing diffs for swallowed errors, empty catch blocks, or ignored error returns."

Enumerate the concrete checks (swallowed errors, silent fallbacks, overly broad catches, ignored returns) to raise specificity and trigger-term coverage.

Mention supported languages or file types to sharpen distinctiveness and trigger terms.

DimensionReasoningScore

Specificity

"Validate error handling completeness" names the domain and one concrete action (validate), but does not enumerate the specific violation types it checks, leaving coverage non-comprehensive.

3 / 5

Completeness

It gives a clear "what" (validate error handling completeness) but provides no "Use when..." clause or trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

"error handling", "completeness", and "languages" are relevant but generic; it lacks the natural phrases users would say like "swallowed errors", "empty catch", or "ignored returns".

3 / 5

Distinctiveness Conflict Risk

"error handling completeness across languages" carves a distinct niche with minimal overlap risk, though it sits near language-specific style validators that also touch error handling.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

peteski22/agent-pragma

Path

plugins/pragma/skills/error-handling/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.