error-handling-patterns

Build resilient applications with robust error handling strategies that gracefully handle failures and provide excellent debugging experiences.

Quality

25%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/error-handling-patterns/SKILL.md

The canonical home for this skill is error-handling-patterns in rmyndharis/antigravity-skills

Quality

Content

18%Scale 1-5

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

This skill is essentially a placeholder with no actionable content. It provides no concrete error handling patterns, code examples, or specific guidance — everything is deferred to a resource file that doesn't exist in the bundle. The instructions are generic boilerplate that could apply to any skill topic and provide no value specific to error handling.

Suggestions

Add concrete, executable code examples for at least 2-3 core error handling patterns (e.g., custom exception hierarchies, retry with backoff, circuit breaker) directly in the SKILL.md.

Replace the generic instruction bullets ('Clarify goals', 'Apply best practices') with specific, actionable steps for implementing error handling, such as a workflow for designing error boundaries or choosing between retry strategies.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns so the skill has standalone value.

Add a concrete workflow with validation steps, e.g., 'Define error types → Implement handlers → Test with failure injection → Verify error messages are actionable'.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are padded with obvious items that don't add value. The instructions section is generic boilerplate ('Clarify goals, constraints, and required inputs') rather than skill-specific content. However, it's not excessively verbose overall.	3 / 5
Actionability	The skill provides zero concrete code, commands, or specific guidance. Instructions like 'Apply relevant best practices and validate outcomes' are entirely vague. Everything actionable is deferred to a resource file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The four bullet points in Instructions are generic platitudes ('Clarify goals', 'Apply best practices', 'Provide actionable steps') with no sequencing, no validation checkpoints, and no specificity to error handling.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in theory. However, the bundle has no files, so the reference is unverifiable and the SKILL.md itself contains almost no substantive content — it's an empty shell pointing to a nonexistent resource.	2 / 5
	Total	7 / 20 Passed

Description

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

This description reads more like a marketing tagline than a functional skill description. It uses aspirational language ('robust', 'gracefully', 'excellent') without specifying concrete actions or providing trigger guidance for when Claude should select it. The lack of a 'Use when...' clause and the vague, buzzword-heavy phrasing significantly reduce its effectiveness for skill selection.

Suggestions

Add a 'Use when...' clause with specific trigger phrases like 'Use when the user asks about error handling, exception management, try-catch patterns, retry logic, or debugging strategies'.

Replace vague aspirational language with concrete actions, e.g., 'Implements try-catch blocks, creates custom error classes, adds retry logic, configures error logging, and builds circuit breakers'.

Include natural synonyms and related terms users might say, such as 'exceptions', 'stack traces', 'error messages', 'fault tolerance', and 'error recovery'.

Dimension	Reasoning	Score
Specificity	Names the domain ('error handling') but the actions are vague and abstract — 'gracefully handle failures' and 'provide excellent debugging experiences' are aspirational statements rather than concrete actions like 'implement try-catch blocks' or 'create custom error classes'.	2 / 5
Completeness	Has a vague 'what' (build resilient applications with error handling) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which per the rubric caps completeness at 3, and the weak 'what' brings it down to 2.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'error handling', 'failures', and 'debugging', but misses many natural terms users would say such as 'exceptions', 'try-catch', 'error messages', 'stack traces', 'logging', 'retry logic', or 'fault tolerance'.	3 / 5
Distinctiveness Conflict Risk	Very broad — 'build resilient applications' could overlap with general coding skills, testing skills, logging skills, or architecture skills. The description doesn't carve out a clear niche that distinguishes it from other development-related skills.	2 / 5
	Total	9 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/error-handling-patterns/SKILL.md
Commit: 57c135b

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.