error-handling-patterns
Build Reliable Error Handling
Unhandled failures obscure root causes and weaken application reliability. This skill applies typed errors, retries, circuit breakers, cleanup, and graceful degradation across common programming languages.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "error-handling-patterns" from https://skillstore.io/skills/sickn33-error-handling-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-error-handling-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "error-handling-patterns". A payment service retries every exception immediately and returns a generic failure.
Expected outcome:
- Classify timeouts and rate limits as retryable; reject validation and authentication failures immediately.
- Use bounded exponential backoff with jitter and record the final cause.
- Add a circuit breaker and test open, half-open, and recovery states.
Using "error-handling-patterns". A TypeScript API leaks stack traces and uses different error shapes across routes.
Expected outcome:
- Introduce typed application errors with stable codes and status mappings.
- Return safe client messages while retaining stack traces in protected logs.
- Test each error category and verify that internal details never reach responses.
Using "error-handling-patterns". An order workflow can charge a customer before a later database update fails.
Expected outcome:
- Treat payment and order updates as a coordinated workflow with explicit partial-failure states.
- Use idempotency keys and a compensation step for completed charges.
- Record correlation details and test repeated requests, timeouts, and compensation failures.
Security Audit
SafeAll 16 static findings are false positives. The backticks are Markdown references or JavaScript template literals, network calls are illustrative examples, and flagged identifiers are ordinary sample code. No prompt injection, exfiltration intent, or executable automation was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-error-handling-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-error-handling-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-error-handling-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-error-handling-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-error-handling-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). error-handling-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-error-handling-patterns/audits/5BibTeX citation
@techreport{sickn33-sickn33-error-handling-patterns-2026,
author = {sickn33},
title = {error-handling-patterns security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-error-handling-patterns/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "error-handling-patterns security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-error-handling-patterns/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-error-handling-patterns:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-error-handling-patterns
2026-08-21
wshobson-error-handling-patterns
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize API Errors
Define typed failures, stable error codes, safe client messages, and consistent status mappings for an application API.
Protect External Dependencies
Add bounded retries, timeouts, circuit breakers, and fallbacks around unreliable services without hiding the original cause.
Review Team Practices
Create shared guidance for logging, cleanup, error propagation, async failures, and focused reliability tests.
Try These Prompts
Review this function and add clear validation, typed errors, cleanup, and useful messages. Explain each change and suggest focused tests.
Design an error model for this API. Define categories, status mappings, stable codes, safe client messages, logging context, and tests.
Refactor this service call with bounded retries, exponential backoff, timeout handling, and a circuit breaker. Preserve the original error context.
Audit this distributed workflow for partial failures and cascading risk. Propose idempotency, compensation, graceful degradation, aggregation, observability, and chaos-test scenarios.
Best Practices
- Classify failures before choosing retry, fallback, propagation, or termination behavior.
- Preserve the original cause and useful context while keeping sensitive details out of user-facing messages.
- Verify failure paths with focused tests, cleanup checks, and observable recovery behavior.
Avoid
- Do not catch broad exceptions unless the handler can recover, add context, or rethrow safely.
- Do not retry validation, authentication, or other permanent failures.
- Do not swallow async errors or return generic messages without preserving diagnostic context.
Frequently Asked Questions
Which programming languages does this skill cover?
Can it choose between exceptions and Result types?
Does it implement retries and circuit breakers automatically?
Can it improve production error messages?
Does it support distributed system failures?
What information should I provide?
Developer Details
Author
sickn33License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-handling-patternsRef
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
6 downloads · 136 views
File structure