error-handling

Implements error handling patterns, structured logging, retry strategies, circuit breakers, and graceful degradation. Use when designing error handling, setting up logging, implementing retries, adding error tracking, or when asked about error boundaries, log aggregation, alerting, or resilience patterns.

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

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.

Highly actionable, executable content with excellent WRONG/CORRECT contrast patterns and a clear stepwise workflow. Its main weaknesses are modest: a slightly redundant log-levels guide and a monolithic single-file structure where per-language material could be split into reference files.

Suggestions

Move the per-language pattern sections (JavaScript/TypeScript, Python, Go) into references/ files (e.g., references/typescript.md, references/python.md, references/go.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Trim or condense the log-levels guide to only the skill-specific guidance (production default INFO, never-log list), dropping the standard TRACE-DEBUG-INFO-WARN-ERROR-FATAL definitions Claude already knows.

Turn the Step 7 anti-patterns validation into an explicit feedback loop: check each anti-pattern, fix violations in the relevant layer, and re-validate until the checklist passes — and add brief supporting guidance for Step 1 (error taxonomy) so every checklist step has a corresponding section.

Dimension	Reasoning	Score
Conciseness	The body is dominated by tight WRONG/CORRECT code contrasts with almost no filler prose, but the log-levels guide restates standard knowledge Claude already has ("TRACE: Extremely detailed (loop iterations...)"), and a few code comments are redundant.	4 / 5
Actionability	Fully executable, copy-paste-ready examples across TypeScript, Python, and Go — a complete AppError hierarchy, pino config with redaction, a withRetry implementation with jitter and retryOn predicates, a full CircuitBreaker class, and concrete Sentry setup — with specific defaults (maxRetries 3, baseDelay 1000).	5 / 5
Workflow Clarity	The 7-step checklist ("Step 1: Define error taxonomy... Step 7: Validate against anti-patterns checklist") gives a clear sequence with an explicit validation step backed by the anti-patterns table. It falls short of a 5 because validation is a one-time final step rather than a validate-fix-retry feedback loop, and Step 1 (error taxonomy) has no supporting section.	4 / 5
Progressive Disclosure	Sections are clearly organized, but this is a ~480-line monolithic SKILL.md with no references at all — per-language pattern guides, structured logging details, and Sentry setup are all inlined content that plausibly belongs in separate references/ files.	3 / 5
	Total	16 / 20 Passed

Description

88%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 description that clearly states both capabilities and explicit use-when triggers with natural phrasing. Its only weaknesses are a few missing common synonyms (e.g., "exceptions", "try/catch") and minor overlap risk with hypothetical logging/monitoring-focused skills.

Dimension	Reasoning	Score
Specificity	The description lists five distinct concrete capabilities ("error handling patterns, structured logging, retry strategies, circuit breakers, and graceful degradation"), matching the anchor for multiple specific concrete actions with comprehensive coverage.	5 / 5
Completeness	It explicitly answers both "what" (first sentence enumerating capabilities) and "when" ("Use when designing error handling... or when asked about error boundaries, log aggregation, alerting, or resilience patterns") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Trigger phrases are natural and varied ("designing error handling, setting up logging, implementing retries, adding error tracking... error boundaries, log aggregation, alerting, or resilience patterns"), but common synonyms a user would naturally say — such as "exceptions", "exception handling", or "try/catch" — are missing.	4 / 5
Distinctiveness Conflict Risk	It carves out a distinct resilience/error-handling niche with recognizable triggers (circuit breakers, retry strategies, error boundaries), but its logging, alerting, and log-aggregation scope creates minor overlap risk with a dedicated logging or observability skill.	4 / 5
	Total	18 / 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: CloudAI-X/claude-workflow-v2
Path: skills/error-handling/SKILL.md
Commit: 3b5a89e

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