error-handling

Error handling with wellcrafted trySync/tryAsync and toastOnError. Use for try-catch, Result types, error toasts, HTTP errors.

Quality

86%

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

72%

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

A dense, actionable error-handling reference with executable code and clean progressive disclosure. Its main weakness is verbosity in the rationale sections and prose-driven decision guidance rather than crisp sequenced workflows.

Suggestions

Trim the explanatory rationale blocks (e.g. 'Why', 'Reading intent', 'Avoids coincidental behavior') to one line each or move them into a reference file to improve conciseness.

Convert the 'When to split the checks' vs 'When combining is OK' guidance into a short explicit decision list or table so the branching logic is unambiguous.

Add a one-line validation/testing checkpoint near the logging section (e.g. 'assert via memorySink, never console output') framed as an explicit step to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly high-signal project-specific knowledge with no basic-concept padding, but several rationale sections ('Why', 'Reading intent', 'Avoids coincidental behavior') add explanatory prose that could be tightened to earn the top token-efficiency anchor.	2 / 3
Actionability	Multiple complete, copy-paste-ready TypeScript blocks (trySync/tryAsync, Err-wrapping, RPC adapters, memorySink tests) give fully executable guidance, matching the top anchor.	3 / 3
Workflow Clarity	Numbered Key Rules and clear if/else examples sequence the patterns, but the split-vs-collapse decision guidance is prose-driven with no explicit validation/feedback checkpoint; as a pattern skill it sits just below the crisp-workflow top anchor.	2 / 3
Progressive Disclosure	A well-signaled '## References' section maps each working context to a real one-level-deep file (all four referenced files exist), with cross-links to related skills, matching the clear-overview top anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 tight, third-person description that states concrete capabilities and gives explicit use-when triggers with natural keywords. It clearly distinguishes itself via library-specific tooling.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities tied to a specific library ('wellcrafted trySync/tryAsync and toastOnError') rather than vague actions, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (error handling with trySync/tryAsync and toastOnError) and 'when' (the 'Use for ...' trigger clause), matching the top anchor.	3 / 3
Trigger Term Quality	'Use for try-catch, Result types, error toasts, HTTP errors' provides good coverage of natural terms a developer would actually say, including common variations.	3 / 3
Distinctiveness Conflict Risk	Anchored to a specific niche (wellcrafted Result helpers, toastOnError) with distinct triggers unlikely to conflict with generic skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

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

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.