Error Handling Patterns
Robust error handling patterns for TypeScript, Python and Go: typed errors, retries, circuit breakers, and user-facing messages that never leak internals.
- What
- Robust error handling patterns for TypeScript, Python and Go: typed errors, retries, circuit breakers, and user-facing messages that never leak internals.
- Cost
- Free
- Needs
- Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me.
- Level
- Beginner — Pinned version: install the code at commit…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: consistent, robust error handling patterns for production applications in TypeScript, Python and Go. Five core principles anchor everything: fail fast and loudly (surface errors at the boundary where they occur, never bury them); typed errors over string messages (errors are first-class values with structure, e.g. an AppError hierarchy with code and statusCode in TypeScript); user messages are not developer messages (friendly text for users, full context logged server-side); never swallow errors silently (every catch block must handle, re-throw or log); and errors are part of your API contract (document every error code a client may receive). Covers designing error types and exception hierarchies, retry logic with backoff and circuit breakers for unreliable dependencies, reviewing API endpoints for missing handling, user-facing failure messages, and debugging cascading failures or silent error swallowing. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: these are patterns to adapt to your stack, not a linter; some teams will disagree on details (exceptions vs result types), pick one convention and hold it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Error Handling Patterns is a free Muse skill with consistent, robust error handling patterns for production applications in TypeScript, Python and Go. Its core principles are fail fast and loudly, surfacing errors at the boundary where they occur, typed errors over string messages, plus retries and circuit breakers, with user-facing messages that never leak internals.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Error Handling Patterns" with your Muse. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/error-handling/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Apply the error handling patterns to [module/service] in [TypeScript/Python/Go]" or "Review [endpoint/module] for missing error handling." 3. Work through the five principles with Muse: typed errors first, then retries and circuit breakers for external calls, then user-facing messages. Tip: start new modules by defining the error hierarchy before writing happy-path code; retrofitting errors is where silent swallowing creeps in. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste real secrets or customer data when asking Muse to review error paths.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.