Error handling patterns across languages — exceptions, Result types, propagation, graceful degradation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Error Handling Patterns
Build resilient applications with robust error handling strategies that gracefully handle failures and provide excellent debugging experiences.
This SKILL.md is a thin index. **Read the relevant `references/<topic>.md` file** only when you need that topic's detail — the code samples and full patterns live there, not here.
## When to Use This Skill
- Implementing error handling in new features
- Designing error-resilient APIs
- Debugging production issues
- Improving application reliability
- Creating better error messages for users and developers
- Implementing retry and circuit breaker patterns
- Handling async/concurrent errors
- Building fault-tolerant distributed systems
## Core Concepts
**Error handling philosophies:**
- **Exceptions** — traditional try-catch, disrupts control flow.
- **Result types** — explicit success/failure, functional approach.
- **Error codes** — C-style, requires discipline.
- **Option/Maybe types** — for nullable values.
**Error categories:**
- **Recoverable** — network timeouts, missing files, invalid user input, API rate limits. Handle and continue (retry, fallback).
…
The line at the top of this page pins the label git:20261020.7a1f356, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3884 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
higoralves/orc · 7 stars · license MIT · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sivov55dwgeuildn
GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/error-handling-patterns
GET https://markdownregistry.com/api/v1/blob/2834de3e589c1900414661c5975712eaf7da746f4052a364d4404e08320c2c65
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
higoralves/orc · orc/skills/adr-writing/SKILL.md · Author and update Architecture Decision Records (ADRs) — the durable record of a decision and its trade-offs, in…
higoralves/orc · orc/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test…
higoralves/orc · orc/skills/callouts/SKILL.md · The orc callout palette — emoji-header blockquotes in conversation, GitHub-flavored [!TYPE] form for GitHub-bound output
higoralves/orc · orc/skills/ci-routing/SKILL.md · The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the…
higoralves/orc · orc/skills/code-discovery/SKILL.md · Use when discovering or navigating a codebase before planning, implementing, debugging, or refactoring — prefer a…
wshobson/agents · plugins/developer-essentials/skills/error-handling-patterns/SKILL.md · Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful…
dicklesworthstone/pi_agent_rust · tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/error-handling-patterns/SKILL.md · Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful…
hermeticormus/libreuiux-claude-code · plugins/developer-essentials/skills/error-handling-patterns/SKILL.md · Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful…
hermeticormus/claude-code-game-development · plugins/developer-essentials/skills/error-handling-patterns/SKILL.md · Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful…
rudycity/superagent · .agents/skills/error-handling-patterns/SKILL.md · Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful…
event4u-app/agent-config · src/skills/error-handling-patterns/SKILL.md · Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/error-handling-patterns/SKILL.md · Design and review error handling in a codebase: which errors are expected results versus bugs, typed error hierarchies…
khaledsaeed18/dotclaude · skills/engineering/error-handling-patterns/SKILL.md · Design and review error handling in a codebase: which errors are expected results versus bugs, typed error hierarchies…
