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

—

Does it follow best practices?

Impact

95%

1.39x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is rich with concrete, executable code across multiple languages, making it highly actionable. However, it is verbose (explaining concepts Claude already knows), lacks sequenced workflows with validation checkpoints, and references bundle files that are not actually present.

Suggestions

Trim the "Core Concepts" section that explains basics Claude already knows (exceptions vs Result types, recoverable/unrecoverable categories) and lead directly with the concrete patterns to improve conciseness.

Resolve the "Resources" references: either create the listed references/*.md, assets/*.md, and scripts/*.py files and move the detailed language-specific patterns into them (keeping SKILL.md a lean overview), or remove the broken references.

For multi-stage examples like process_order, add explicit validation checkpoints (validate input → proceed only if valid → handle payment with retry → verify result) so the workflow shows a clear validate-fix-retry sequence.

Dimension	Reasoning	Score
Conciseness	The "Core Concepts" section explains basic knowledge Claude already has (exceptions vs Result types, recoverable/unrecoverable categories) and the same patterns are repeated across four languages, so it is mostly efficient but padded with unnecessary explanation and could be tightened.	2 / 3
Actionability	The body provides extensive fully-executable, copy-paste-ready code across Python, TypeScript, Rust, and Go plus circuit breaker, error aggregation, and graceful degradation implementations with usage examples.	3 / 3
Workflow Clarity	It is a pattern catalog rather than a sequenced workflow; some examples like process_order show ordered error handling, but there are no explicit validation checkpoints or validate-fix-retry feedback loops.	2 / 3
Progressive Disclosure	The ~640-line body keeps detailed language-specific content inline that should be split out, and the "Resources" section references files (references/.md, assets/.md, scripts/*.py) that do not exist in the bundle, so structure is present but references are broken and content is not appropriately split.	2 / 3
	Total	9 / 12 Passed

Description

92%

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, well-structured description that explicitly states both capabilities and trigger conditions with concrete, natural language. Its only weakness is that two of its three triggers are broad enough to risk overlap with adjacent skills.

Dimension	Reasoning	Score
Specificity	"Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation" enumerates multiple specific concrete patterns, matching the anchor that lists several specific actions rather than just naming a domain.	3 / 3
Completeness	It clearly answers both what ("Master error handling patterns... including exceptions, Result types...") and when ("Use when implementing error handling, designing APIs, or improving application reliability"), with an explicit Use-when trigger clause.	3 / 3
Trigger Term Quality	"Use when implementing error handling, designing APIs, or improving application reliability" provides explicit, natural phrases a user would say when needing this skill, giving good keyword coverage rather than just one relevant term.	3 / 3
Distinctiveness Conflict Risk	The error-handling niche is clear, but the triggers "designing APIs" and "improving application reliability" are broad and could overlap with API-design or reliability skills, so it is not a clear niche with fully distinct triggers.	2 / 3
	Total	11 / 12 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
Commit: e9f9b67

Reviewed: 4 days 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.