error-handling-patterns

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

Quality

38%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/error-handling-patterns/SKILL.md

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

Quality

Content

32%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 skill body is token-efficient and reasonably structured, but it provides no concrete, executable guidance — only generic platitudes — and its sole reference points to a file that is missing from the bundle. Workflow steps are abstract with no real validation checkpoints.

Suggestions

Add concrete, executable guidance: small code snippets or specific steps for retry/backoff, circuit breakers, and structured error logging instead of generic bullets.

Create the referenced `resources/implementation-playbook.md` (or remove the dangling reference) so progressive disclosure actually resolves.

Turn the Instructions into a real sequenced workflow with explicit validation checkpoints (e.g., 'reproduce the error -> add handling -> verify the failure path is covered').

Dimension	Reasoning	Score
Conciseness	The body is short and lean with no over-explanation of concepts Claude already knows; only minor redundancy (the description is repeated verbatim and a few generic instruction bullets) keeps it just below a 5.	4 / 5
Actionability	The instruction bullets ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') are vague platitudes with no concrete code, commands, or specific patterns, and the only pointer is to a missing file, matching anchor 1 ('entirely vague or abstract; only describes rather than instructs').	1 / 5
Workflow Clarity	A rough generic sequence exists (clarify goals -> apply best practices and validate -> provide steps and verification) but steps are poorly defined and validation is mentioned only abstractly with no real checkpoints, matching anchor 2.	2 / 5
Progressive Disclosure	Sections are present and the one reference to `resources/implementation-playbook.md` is clearly signaled, but that file does not exist in the bundle, so the disclosed detail is unreachable and navigation fails, matching anchor 2.	2 / 5
	Total	9 / 20 Passed

Description

45%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 states a clear purpose around error handling and debugging but remains abstract, with no concrete actions and no explicit 'Use when...' trigger guidance. It is adequately specific to its niche yet risks overlap with adjacent reliability skills.

Suggestions

Replace abstract phrases with concrete actions, e.g., 'implement retry/backoff, circuit breakers, structured error logging, and user-friendly error messages'.

Add an explicit trigger clause: 'Use when implementing error handling, designing fault-tolerant APIs, or debugging production failures.'

Include natural synonyms users say (exceptions, retries, try/catch, error messages) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Phrases like 'Build resilient applications', 'gracefully handle failures', and 'provide excellent debugging experiences' name the error-handling domain but use abstract capability language with no concrete actions (e.g., implement retry, wrap in try/catch), matching anchor 2.	2 / 5
Completeness	A clear 'what' is present but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3 (anchor: clear 'what', 'when' missing).	3 / 5
Trigger Term Quality	Natural terms 'error handling' and 'debugging' are present, but common variations/synonyms users say ('exceptions', 'retries', 'error messages', 'try/catch') are missing, matching anchor 3 rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	It is specific to error handling but very broad and overlaps with many reliability, debugging, and API-design skills, matching anchor 3 ('somewhat specific but could still overlap with similar skills').	3 / 5
	Total	11 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/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.