CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable with extensive executable code, but it is verbose across multiple languages and monolithic with no progressive disclosure into reference files. Workflow sequencing is present but lacks intermediate validation checkpoints.

Suggestions

Split per-language patterns and the retry/circuit-breaker/logging sections into separate reference files (e.g., references/python.md, references/retry.md) and keep SKILL.md as an overview, improving conciseness and progressive disclosure.

Tighten or remove content Claude already knows, such as the TRACE/DEBUG/INFO log-level definitions and the recap anti-patterns table, or move them to a reference.

Add intermediate validation checkpoints to the 7-step workflow (e.g., verify the error hierarchy compiles and logs render as JSON before moving to retries) rather than only validating at the final step.

DimensionReasoningScore

Conciseness

Mostly code-driven and efficient, but ~480 lines repeat the same patterns across three languages and includes basics Claude already knows (the TRACE/DEBUG/INFO log-level guide and the recap anti-patterns table), so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready code in TypeScript, Python, and Go (custom error hierarchies, withRetry, CircuitBreaker, Sentry setup) with concrete WRONG/CORRECT contrasts.

3 / 3

Workflow Clarity

A 7-step checklist gives a clear sequence and a terminal 'Validate against anti-patterns checklist' step, but there are no intermediate validation checkpoints or fix-and-retry feedback loops between steps.

2 / 3

Progressive Disclosure

Well-sectioned with headers, but it is a single ~480-line monolithic file with no bundle references; per-language patterns, retry/circuit-breaker, and logging guides could be split into separate reference files.

2 / 3

Total

9

/

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 strong, third-person description that concretely names capabilities and pairs them with an explicit, well-covered 'Use when' trigger clause. Voice and trigger coverage both meet the top anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'error handling patterns, structured logging, retry strategies, circuit breakers, and graceful degradation' — matching the anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Implements error handling patterns...') and when ('Use when designing error handling, setting up logging...'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasing well: 'error handling', 'setting up logging', 'implementing retries', 'error tracking', 'error boundaries', 'log aggregation', 'alerting', 'resilience patterns', which are terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The error-handling/observability niche has distinct, specific triggers (circuit breakers, retry strategies, error boundaries) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
CloudAI-X/claude-workflow-v2
Reviewed

Table of Contents

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.