Error Handling Patterns
Robust error handling: exceptions vs Result types, retry, circuit breakers
- What
- Robust error handling: exceptions vs Result types, retry, circuit breakers
- Cost
- Free
- Needs
- an application to make more resilient (any language)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an error handling patterns skill for building resilient applications: error philosophies compared (exceptions vs Result types vs error codes vs Option types, and when each fits), error categories (recoverable vs unrecoverable), retry and circuit-breaker patterns, fault-tolerant distributed design — with detailed worked patterns in `references/details.md`. Best practices included: fail fast, preserve context, meaningful messages, log appropriately. By @wshobson, listed here with credit to its creator. Honest caveats: language-agnostic guidance — you translate the patterns to your stack; the deep material is in the reference file, so the agent needs to open it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an application to make more resilient (any language) Install "Error Handling Patterns" for me. Robust error handling: exceptions vs Result types, retry, circuit breakers Repository: https://github.com/wshobson/agents/blob/main/plugins/developer-essentials/skills/error-handling-patterns/SKILL.md 1. Fetch the SKILL.md file for the wshobson-error-handling-patterns skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "wshobson-error-handling-patterns". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.