Thrunt Debug
Orchestrates a scientific-method debug session in an isolated subagent
Test report
- Verdict
- Tested · Didn't pass
- Tested
- Jul 18, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Jul 30, 2026 · 0197e5c
⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (repo unreachable/deleted). The test below is what we measured on Jul 18, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.
Copied on its own the skill folder is just an orchestrator shell: its very first step runs node .github/thrunt-god/bin/thrunt-tools.cjs and then delegates all real work to a thrunt-incident-debugger subagent, neither of which is co-located with the skill or present in a normal project. It only functions after the entire thrunt-god framework and its custom agents are installed, so no standalone output delta could be demonstrated. The SKILL.md is a clean, well-structured checkpoint/continuation protocol with no security issues, but as an installed unit it is inert without its engine.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 4/5
- Triggers reliably 4/5
- Output vs. baseline 3/10
- Docs & honesty 4/5
What Thrunt Debug does
A debugging orchestrator that gathers symptoms, spawns a thrunt-incident-debugger subagent with a fresh context, and persists a debug session file across context resets. Triggers on requests to systematically investigate, reproduce, and fix a bug. Requires the full thrunt-god framework to be installed.
How to install Thrunt Debug
Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.
Commands — how to trigger Thrunt Debug
-
/thrunt-debugOrchestrates a scientific-method debug session in an isolated subagent
It also activates on plain-language prompts like these:
-
Systematically investigate why this bug keeps happening across resets. -
Start a debug session that persists state even if context gets reset. -
I need a scientific-method investigation into this recurring crash.
Frequently asked questions
- Is the Thrunt Debug skill free?
- Yes. The skill itself is free from backbay-labs/thrunt-god. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Thrunt Debug work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 18, 2026. Verdict: Tested · Didn't pass. Copied on its own the skill folder is just an orchestrator shell: its very first step runs node .github/thrunt-god/bin/thrunt-tools.cjs and then delegates all real work to a thrunt-incident-debugger subagent, neither of which is co-located with the skill or present in a normal project. It only functions after the entire thrunt-god framework and its custom agents are installed, so no standalone output delta could be demonstrated. The SKILL.md is a clean, well-structured checkpoint/continuation protocol with no security issues, but as an installed unit it is inert without its engine.
- How do I install Thrunt Debug?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Thrunt Debug with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.