CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

76%

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

65%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 is well-structured with a model progressive-disclosure setup: a lean overview pointing to a real, clearly signaled reference file, plus actionable best practices, pitfalls, and a concrete code example. Its weaknesses are the Claude-known "Core Concepts" and redundant "When to Use" sections that spend tokens without adding value, and the absence of a sequenced decision workflow for choosing among the patterns.

Suggestions

Cut or drastically compress the "Core Concepts" section (exceptions vs. Result types, recoverable vs. unrecoverable lists) — Claude already knows this material — and move any genuinely non-obvious categorization into references/details.md.

Drop the "When to Use This Skill" section or fold it into one line, since it duplicates the description's "Use when..." triggers almost verbatim.

Add a short ordered decision flow (categorize the error → pick the mechanism → apply the pattern → verify cleanup/logging) so the patterns translate into a sequence Claude can follow.

DimensionReasoningScore

Conciseness

Roughly a third of the body explains concepts Claude already knows — the "Core Concepts" section catalogs exceptions vs. Result types and obvious error categories ("Network timeouts", "Out of memory", "Stack overflow", "Programming bugs (null pointer, etc.)"), and "When to Use This Skill" restates the description's triggers. The remainder (best practices, pitfalls, code example) is lean, which keeps this at anchor 3's "mostly efficient but includes some unnecessary explanation" rather than dropping to 2, since the padding is terse bullets rather than verbose prose.

3 / 5

Actionability

The numbered "Best Practices" ("Use try-finally, context managers, defer"), the "Common Pitfalls" list, and a concrete Python example with error wrapping and `from e` chaining give mostly executable guidance, matching anchor 4. It falls short of 5 because the example depends on undefined project-specific names (db, payment_service, ValidationError, ApplicationError) so it is not copy-paste ready, and only Python is shown inline despite the "across languages" scope.

4 / 5

Workflow Clarity

There is no sequenced decision procedure for applying the patterns — the closest is the brief "When to Use Each" list ("Exceptions: Unexpected errors", "Result Types: Expected errors"), which offers partial direction without an ordered flow or checkpoints. This fits anchor 3 (guidance present but gaps); it is not a simple single-action skill that would qualify for 5, and no destructive/batch cap applies.

3 / 5

Progressive Disclosure

The body is a genuine overview tier with a single, well-signaled, one-level-deep reference — "Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient" — and the referenced file exists (516 lines of language-specific and universal patterns). This matches anchor 5's clear overview with appropriately split content and easy navigation.

5 / 5

Total

15

/

20

Passed

Description

75%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 description that clearly states what the skill covers and gives an explicit, multi-phrase when-clause in third person. Its main weaknesses are trigger phrases that drift slightly beyond the skill's niche ("designing APIs", "improving application reliability") and the abstract "Master ... patterns" framing rather than concrete actions.

DimensionReasoningScore

Specificity

The description lists several concrete pattern areas — "exceptions, Result types, error propagation, and graceful degradation" — comparable to anchor 4's "lists several specific actions; minor gaps in coverage". It falls short of 5 because the framing verb "Master ... patterns" is abstract and no concrete per-pattern actions (e.g., wrap errors, add retry logic) are stated.

4 / 5

Completeness

Both parts are present: a clear what ("Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation") and an explicit when ("Use when implementing error handling, designing APIs, or improving application reliability"). It sits between anchors 4 and 5: the when-clause is explicit with three trigger phrases, but "improving application reliability" is generic and "designing APIs" is broader than the skill's scope, so it does not clearly match the fully-concrete anchor 5.

4 / 5

Trigger Term Quality

The when-clause includes natural phrases users would say — "implementing error handling", "designing APIs", "improving application reliability" — giving good but not comprehensive coverage. Common variations like "exceptions", "try/catch", "error messages", or "retry logic" are absent from the triggers, so it matches anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Error handling is a clear niche with an on-point core trigger ("implementing error handling"), matching anchor 4's "mostly distinct; minor overlap risk". It is not a 5 because "designing APIs" and "improving application reliability" are broad enough to also fire for general API-design or code-quality skills.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/developer-essentials/skills/error-handling-patterns/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.