CtrlK
BlogDocsLog inGet started
Tessl Logo

error-handling-patterns

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

61

Quality

72%

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

Quality

Content

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

A well-organized reference skill with a solid executable example and a real, clearly signaled reference file. The main weakness is over-explanation of concepts Claude already knows and the absence of a sequenced workflow with checkpoints.

Suggestions

Trim or move the Core Concepts / error-categories explanations to references/details.md, since Claude already knows what exceptions and recoverable errors are.

Add a brief multi-step workflow with validation checkpoints (e.g., classify error → choose strategy → wrap/preserve context → validate handling via test) to raise workflow clarity.

Include at least one short non-Python example (e.g., a Rust Result or Go error-return snippet) to match the "across languages" claim in the description.

DimensionReasoningScore

Conciseness

The Core Concepts section re-explains error philosophies and recoverable/unrecoverable error categories that Claude already knows, adding padding; the actionable Best Practices, Pitfalls, and code example are efficient.

3 / 5

Actionability

Provides a complete, executable Python example with custom exception hierarchy, wrapping, and logging, plus concrete best-practice and pitfall bullets; minor gaps remain for non-Python languages referenced in the description.

4 / 5

Workflow Clarity

Content is organized into lists but there is no sequenced multi-step workflow with validation checkpoints; it reads as a reference rather than a guided process, which fits the patterns nature but leaves checkpoints implicit.

3 / 5

Progressive Disclosure

The body is an overview with a clearly signaled one-level-deep reference ("Detailed pattern documentation lives in `references/details.md`") that exists as a real file; the inlined Core Concepts could arguably move to details, leaving minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

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

A strong, third-person description that clearly conveys both capability and trigger conditions with concrete named patterns. Minor gains are possible by trimming the generic "designing APIs" trigger and adding a few more natural user phrases.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete patterns ("exceptions, Result types, error propagation, and graceful degradation") rather than vague language, though these are concepts rather than discrete actions, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly states what the skill masters (error handling patterns across languages with named techniques) and when to use it via a concrete "Use when..." clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

The "Use when implementing error handling, designing APIs, or improving application reliability" clause supplies natural phrases a user would say, though a few common variants (e.g. "try-catch", "error recovery") are missing.

4 / 5

Distinctiveness Conflict Risk

"Error handling patterns" is a fairly distinct niche, but the broad "designing APIs" trigger introduces minor overlap risk with general API-design skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.