All 94 skillsQuality1 of 13
stryx:debug
Something is broken: a bug, an error, a crash, a failing test or wrong data.
/stryx:debugInside its piece: 25 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- 22reference files
- 1helper scripts
- 25files in the skill
- 314KB on disk
- 15chapters
- 3agents work by this book
Use it when
in the skill’s own wordsWhen anything fails or behaves wrong
- a bug
- error
- crash
- exception
- stack trace
- failing or flaky test
- broken build or type-check
- white screen
- hang or freeze
- regression ("it worked before")
- wrong
- stale or missing data
- an app that slows down or leaks memory
- 401/403
- cookie or session trouble
- When the user says
- broken
- not working
- wrong output
- fix this
- debug
- why does this fail
- keeps failing
- stuck
- Also when an earlier fix attempt failed, when another skill hands over a failing check
Not for
another skill does it- Proving finished work is done→ stryx:verify
- Writing new feature tests→ stryx:test
- Designing error handling while building→ stryx:error-handling
- An unreachable host or port→ stryx:networking
- Driving a known list of checks green→ stryx:execute loop mode
What it covers
14 parts- root-cause-first diagnosis
- retry and escalation limits
- references for Electron
- IPC
- sql.js
- Zustand
- React
- TypeScript
- Vite
- network
- cookies
- memory
- performance
- git bisect and VBA
On its shelf
25 files, 314 KB- references/22
- SKILL.md1
- evals/1
- scripts/1
Inside the book
15 chapters, by title only- Procedure in short
- Core principles
- Safety while debugging
- Retry budget and the 3-strike stop
- The report
- Debug Summary
- The protocol
- Dispatching a subagent to debug
- Time-boxed escalation
- Verification gates
- Bug classification
- Common mistakes and red flags
- Self-diagnosis when debugging stalls
- Logging that finds bugs
- Quick reference: common bug patterns
Its helpers
3 agents work by this book- stryx:debuggerSomething is broken and the hunt would fill the chat: it finds the root cause and fixes it.
- stryx:orion-expertWhen a question is about Orion Studio Pro: how a part works, or whether a number is right.
- stryx:sync-engine-expertWhen Orion's sync or its encryption misbehaves: data vanished, came back old or never arrived.
Works with
the skills it names most- stryx:error-handling→When building code that must fail well: retries, timeouts, fallbacks and messages people can read.
- stryx:learn→You say "remember this" or wrap up a session: the lessons are saved for next time.
- stryx:verify→When Claude is about to say done, fixed or ready to commit: fresh proof comes first.
- stryx:ai-power→When you are not sure which skill fits, or you say "load aipower": it is the map of all skills.
- stryx:containers→When putting an app in Docker, or reading the logs and alerts of a running one.
- stryx:networking→Something cannot connect: a port in use, a firewall, DNS, or one PC that cannot see another.
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.