All 94 skillsQuality10 of 13
stryx:error-handling
When building code that must fail well: retries, timeouts, fallbacks and messages people can read.
/stryx:error-handlingInside its piece: 10 specks, one for each file on its shelf. Its twelve group-mates glow on the open book behind it. The light splits toward orange, the band of Quality.
In numbers
counted 2026-10-12 in the installed set- 8reference files
- 10files in the skill
- 94KB on disk
- 4chapters
- 2agents work by this book
Use it when
in the skill’s own wordsWhen designing or writing the error handling of code you are building
- choosing error types or classes
- deciding where to catch
- rethrow or let it fail
- adding retries with backoff
- timeouts
- a circuit breaker
- fallbacks
- cached or offline data
- feature flags
- draft autosave
- transaction rollback
- the toast
- inline or full-page error messages users will read
- structured error logging
- an API's JSON error body and HTTP status codes
- Also when the user says
- make it resilient
- handle failures gracefully
- what if the server or network is down
- add retry logic
- better error messages
- stop swallowing errors
- fail fast
- asks to check a design for silent catches and lost error context
Not for
another skill does it- Diagnosing a failure that already happened→ stryx:debug
- React error boundary placement and reset→ stryx:react
- VBA handlers→ stryx:vba
- Log format, destinations and telemetry→ stryx:containers
- Scoring a finished change→ stryx:review
Inside the book
4 chapters, by title only- Core procedure
- Principles
- Checklist
- Failure modes of the handling itself
Its helpers
2 agents work by this book- stryx:api-engineerWhen an app must talk to an outside API: a typed client, sign-in, retries.
- stryx:error-handlerWhen error handling should be planned and added before anything breaks.
Works with
the skills it names most- stryx:debug→Something is broken: a bug, an error, a crash, a failing test or wrong data.
- stryx:electron→When working on Electron desktop app code: windows, the bridge between its parts (IPC), tray, menus.
- stryx:react→When building or reviewing React components, hooks and Zustand stores.
- stryx:containers→When putting an app in Docker, or reading the logs and alerts of a running one.
- stryx:security→When code touches logins, permissions, secrets or encryption, or you ask "is this secure".
- stryx:test→When tests must be written or fixed, or you want the test written first (TDD).
Claude loads it by itself when the moment comes; by hand, type the line at the top. It comes with the whole set: Installs all 94 skills, 32 agents and the brain program as one set. The skill’s own text is private source and is not shown here.