error-handling

Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

Quality

81%

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

80%

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

A strong, action-dense reference skill with executable patterns across TypeScript, Python, and Go and a useful pre-merge checklist. Its main gaps are the absence of a sequenced validation workflow and the lack of progressive disclosure — all detail lives inline in one large file.

Suggestions

Move the per-language detailed implementations (TypeScript Result pattern, React Error Boundary, Go sentinel errors) into separate reference files under references/ and keep SKILL.md as a concise overview that links to them with 'See [TS.md](TS.md)' style navigation.

Add a short sequenced workflow for the most common multi-step task — e.g. '1. Define an AppError hierarchy, 2. Wire a global handler, 3. Verify with the checklist' — with an explicit validation/verification checkpoint before merging.

Tighten the API error handler example by including the missing `zod` import so the code is fully runnable as written.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and lean — it jumps straight into executable patterns (typed error classes, Result type, retry with backoff) without explaining basic concepts Claude already knows, and inline comments are limited to non-obvious gotchas like the `Object.setPrototypeOf` `instanceof` fix.	3 / 3
Actionability	It provides fully executable, copy-paste-ready implementations across all three languages (e.g. the `withRetry` function, the FastAPI `@app.exception_handler`, the Go `errors.Is` switch), not pseudocode or vague direction.	3 / 3
Workflow Clarity	This is a pattern catalog rather than a sequenced multi-step workflow; the closing 'Error Handling Checklist' supplies some validation guidance, but there is no explicit step-by-step process with validation checkpoints or feedback loops, which keeps it below a 3.	2 / 3
Progressive Disclosure	The file is well-organized into clear sections (above a 1), but it is a monolithic ~370-line SKILL.md with all per-language detail inline and no reference files or signaled one-level-deep navigation — matching the anchor where 'content that should be separate is inline.'	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-scoped description that names concrete capabilities and natural trigger terms with low conflict risk. Its only real gap is the missing explicit 'Use when...' trigger guidance, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming trigger scenarios — e.g. 'Use when designing error hierarchies, adding retry/circuit-breaker logic, or reviewing endpoints for missing error handling.'

Include a couple of common synonym terms a user might say ('exceptions', 'try/catch') alongside the existing trigger keywords to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	It lists multiple specific concrete patterns — 'typed errors, error boundaries, retries, circuit breakers, and user-facing error messages' — which matches the anchor for listing several specific concrete items rather than the level below's 'some actions, not comprehensive.'	3 / 3
Completeness	It clearly states the 'what' (patterns covered, three languages) but provides no explicit 'when' guidance — there is no 'Use when...' clause or equivalent trigger, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It covers several natural terms a developer would actually say when needing this skill — 'error handling', 'retries', 'error messages', 'circuit breakers' — going well beyond the single-keyword anchor at level 2.	3 / 3
Distinctiveness Conflict Risk	The focused combination of error-handling patterns across three named languages with five specific sub-topics forms a clear niche unlikely to trigger for unrelated skills, matching the distinct-triggers anchor.	3 / 3
	Total	11 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/error-handling/SKILL.md
Commit: 754b8dd

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