error-handling

Apply Wellcrafted Result patterns to fallible operations and preserve failures at boundaries. Use when replacing try/catch, adding trySync or tryAsync, choosing fallback or propagation, or mapping errors.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Well-structured, actionable guidance with clean progressive disclosure and a closing validation checklist. The main improvements are minor tightening of prose and one or two additional complete examples.

Suggestions

Condense the "Source Of Truth" section to a one-line authority pointer plus the read-trigger list; the version-drift and DeepWiki narrative can be trimmed without losing the rule.

Add a complete copy-paste example for the fallback case (returning Ok(fallback) from catch) and the typed defineErrors factory-return case so the common branches are fully executable without inference.

Reframe the Final Check as an explicit feedback loop — e.g. "if any check fails, revise the contract choice and re-verify" — to strengthen validation framing.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — tables, bullets, and short snippets — and assumes Claude's familiarity with Result/try-catch, but the "Source Of Truth" narrative (version drift, DeepWiki-as-leads) is somewhat padded and could be tightened.	4 / 5
Actionability	A contract→pattern decision table plus executable tryAsync and unwrap snippets give mostly concrete guidance, but there is no complete copy-paste example for the fallback-Ok or typed-factory-return cases a reader must currently infer.	4 / 5
Workflow Clarity	The decision flow is clearly sequenced (Choose The Contract → Cross The Boundary → Consume Every Err → Own The Promise → Final Check) and ends with a 5-point verification checklist, but it is a decision framework rather than a validate→fix→retry loop.	4 / 5
Progressive Disclosure	The body is a concise overview with three well-signaled, one-level-deep references (wrapping-boundaries.md, toast-on-error.md, http-boundaries.md), each prefaced by a "Read ... when ..." trigger; all referenced files exist.	5 / 5
	Total	17 / 20 Passed

Description

92%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, specific description with both a clear capability statement and an explicit multi-trigger "Use when" clause. The only gap is missing common synonyms in the trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "preserve failures at boundaries", "replacing try/catch", "adding trySync or tryAsync", "choosing fallback or propagation", and "mapping errors" — giving comprehensive coverage rather than generic phrasing.	5 / 5
Completeness	It explicitly states what it does ("Apply Wellcrafted Result patterns to fallible operations and preserve failures at boundaries") and gives a concrete "Use when..." trigger clause with several named scenarios.	5 / 5
Trigger Term Quality	Natural developer phrases ("try/catch", "trySync", "tryAsync", "fallback", "propagation", "mapping errors") are present, but common synonyms a user might say ("error handling", "catching errors", "error mapping") are not included.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (Result/error boundaries with trySync/tryAsync) and is distinguishable from named sibling skills (define-errors, logging, query-layer, hono), keeping conflict risk minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: EpicenterHQ/epicenter
Path: .agents/skills/error-handling/SKILL.md
Commit: 825a995

Reviewed: 3 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.