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.

1.39x

Quality

65%

Does it follow best practices?

Impact

95%

1.39x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/error-handling-patterns/SKILL.md

The canonical home for this skill is error-handling-patterns in wshobson/agents

Quality

Content

46%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 a comprehensive, code-rich error-handling reference, but it violates progressive disclosure by inlining hundreds of lines that belong in the (currently missing) bundle files and spends tokens restating concepts Claude already knows. Actionability is its strongest dimension thanks to abundant concrete examples.

Suggestions

Move the per-language code catalogs and universal patterns into the referenced files under references/ and assets/, keeping SKILL.md as a concise overview that links out — and actually create those files since the referenced paths do not exist.

Cut the "Core Concepts" section (Exceptions vs Result Types, Error Categories) — these are concepts Claude already knows and add token cost without new guidance.

Make code examples copy-paste runnable by including necessary imports and defining referenced identifiers (e.g., import datetime, define NetworkError/logger) or clearly marking them as illustrative snippets.

Dimension	Reasoning	Score
Conciseness	The 636-line body pads sections with concepts Claude already knows ("Exceptions vs Result Types" definitions, "Recoverable/Unrecoverable Errors" listings), and inlines large code catalogs that belong in reference files, making it noticeably verbose.	2 / 5
Actionability	It provides extensive concrete code examples across Python, TypeScript, Rust, and Go, but many are not strictly copy-paste runnable (missing imports like `datetime`, undefined identifiers like `NetworkError`, `logger`, `db`, and a `try_function` defined after use), leaving minor execution gaps.	4 / 5
Workflow Clarity	The body is a pattern catalog with well-labeled sections but no sequenced multi-step workflow or validation checkpoints; since it involves no destructive/batch operations the cap-at-3 does not apply, yet the absence of any explicit process still caps it at the midpoint.	3 / 5
Progressive Disclosure	The Resources section references files in references/, assets/, and scripts/, but those directories do not exist (dangling references), and the bulk of the content that clearly belongs in separate files is inlined into SKILL.md rather than split out.	2 / 5
	Total	11 / 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 well-crafted description that concretely names the pattern categories it covers and pairs them with an explicit, natural-language "Use when" trigger clause. The main weakness is minor overlap risk from the broad "designing APIs" trigger and a few missing common trigger synonyms.

Dimension	Reasoning	Score
Specificity	"Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation" lists several concrete pattern categories with broad coverage, but stops short of enumerating every action (retry, circuit breakers, async errors) so it is not a full 5.	4 / 5
Completeness	It clearly states what the skill does ("Master error handling patterns across languages...") and explicitly when to use it ("Use when implementing error handling, designing APIs, or improving application reliability"), matching the anchor for explicit what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	"Use when implementing error handling, designing APIs, or improving application reliability" gives good natural trigger phrases a user would say, though common variations like "debugging" or "retry" are absent.	4 / 5
Distinctiveness Conflict Risk	"Error handling patterns across languages" carves a fairly distinct niche with specific triggers, but "designing APIs" creates minor overlap risk with general API-design or debugging skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (642 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	14 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/error-handling-patterns/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.