error-handling-patterns

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

Quality

56%

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

Quality

Content

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

The body is lean and well-structured into clear sections, but it offers almost no executable guidance: instructions are generic bullets with no code or concrete patterns, no sequenced workflow with validation, and the single referenced resource file is missing from the bundle. It reads as a placeholder overview rather than an actionable skill.

Suggestions

Add concrete, executable guidance: example patterns (try/catch, Result type, error propagation) with code snippets instead of abstract 'apply best practices' bullets.

Define a sequenced workflow with validation checkpoints (e.g. identify failure modes -> choose pattern -> implement -> verify error path) rather than a loose bullet list.

Create the referenced 'resources/implementation-playbook.md' (note: path mismatch with 'resources/' vs 'references/') or remove the broken reference.

Dimension	Reasoning	Score
Conciseness	The body is short and assumes Claude's competence without explaining basic concepts, though a few generic lines like 'Apply relevant best practices and validate outcomes' add mild padding.	4 / 5
Actionability	Guidance is high-level and abstract ('Clarify goals', 'Apply relevant best practices') with no concrete code, commands, or specific patterns; the only actionable pointer is a file reference.	2 / 5
Workflow Clarity	Instructions are a loose bullet list with no clear sequence or validation checkpoints, and destructive/batch error-handling work lacks any verify-then-fix feedback loop.	2 / 5
Progressive Disclosure	A reference to 'resources/implementation-playbook.md' is signaled, but that file does not exist in the bundle, so the one-level-deep reference is broken rather than navigable.	2 / 5
	Total	10 / 20 Passed

Description

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

The description is strong: it names a clear domain, lists several concrete patterns, and provides an explicit 'Use when' clause with multiple natural trigger phrases. It uses correct third-person voice and avoids vagueness, with only minor overlap risk on broad triggers like 'designing APIs'.

Suggestions

Add natural user-speak synonyms to the trigger clause (e.g. 'try/catch', 'logging errors', 'error messages') to improve trigger-term coverage.

Tighten the 'designing APIs' trigger to error-specific framing (e.g. 'designing error-resilient APIs or failure modes') to reduce overlap with general API-design skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('exceptions, Result types, error propagation, and graceful degradation') naming the domain, though coverage of patterns is broad rather than exhaustive.	4 / 5
Completeness	Clearly answers 'what' (error handling patterns across languages) and 'when' via an explicit 'Use when...' clause with multiple triggers, though the 'when' could be slightly more specific to edge cases.	4 / 5
Trigger Term Quality	Includes natural trigger phrases like 'implementing error handling', 'designing APIs', and 'improving application reliability' that users would say, but misses common synonyms like 'try/catch', 'logging', or 'error messages'.	4 / 5
Distinctiveness Conflict Risk	The error-handling niche is mostly distinct with clear triggers, though 'designing APIs' and 'improving application reliability' could overlap with general software-design or reliability skills.	4 / 5
	Total	16 / 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: rmyndharis/antigravity-skills
Path: skills/error-handling-patterns/SKILL.md
Commit: 3eff4af

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