Debug Pro

What it does

When your agent uses it

• The user encounters bugs
• Unexpected behavior in their code

Example prompts

• “/debug-pro”

Requirements

• Python 3
• Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Reproduce — Get it to fail consistently. Document exact steps, inputs, and environment.
2. 2Isolate — Narrow scope. Comment out code, use binary search, check recent commits with git bisect.
3. 3Hypothesize — Form a specific, testable theory about the root cause.
4. 4Instrument — Add targeted logging, breakpoints, or assertions.
5. 5Verify — Confirm root cause. If hypothesis was wrong, return to step 3.
6. 6Fix — Apply the minimal correct fix. Resist the urge to refactor while debugging.
7. 7Regression Test — Write a test that catches this bug. Verify it passes.

What it can do on your machine

Read from SKILL.md and the folder at commit b50970c. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • python
  • node
  • curl
  • npm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git, curl and npm, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug Pro loads about 931 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 224 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~87

When it runs · the whole SKILL.md, loaded when a task matches

~931

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteRuns commands with sudoSKILL.md:109

  ermission issue | Check chmod, firewall, sudo |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CraftOS-dev/CraftBot at commit b50970c, republished under its MIT licence (© CraftOS-dev). 224 words, ~931 tokens.

name

debug-pro

description

Advanced debugging assistance and error analysis. Use this skill when the user encounters bugs, errors, crashes, or unexpected behavior in their code. Covers systematic 7-step debugging methodology, language-specific debugging tools (JS/TS, Python, Swift, CSS, Network), git bisect, common error patterns, and quick diagnostic commands.

# Node.js debugger
node --inspect-brk app.js
# Chrome DevTools: chrome://inspect

# Console debugging
console.log(JSON.stringify(obj, null, 2))
console.trace('Call stack here')
console.time('perf'); /* code */ console.timeEnd('perf')

# Memory leaks
node --expose-gc --max-old-space-size=4096 app.js

# Built-in debugger
python -m pdb script.py

# Breakpoint in code
breakpoint()  # Python 3.7+

# Verbose tracing
python -X tracemalloc script.py

# Profile
python -m cProfile -s cumulative script.py

# LLDB debugging
lldb ./MyApp
(lldb) breakpoint set --name main
(lldb) run
(lldb) po myVariable

# Xcode: Product → Profile (Instruments)

/* Outline all elements */
* { outline: 1px solid red !important; }

/* Debug specific element */
.debug { background: rgba(255,0,0,0.1) !important; }

# HTTP debugging
curl -v https://api.example.com/endpoint
curl -w "@curl-format.txt" -o /dev/null -s https://example.com

# DNS
dig example.com
nslookup example.com

# Ports
lsof -i :3000
netstat -tlnp

git bisect start
git bisect bad              # Current commit is broken
git bisect good abc1234     # Known good commit
# Git checks out middle commit — test it, then:
git bisect good  # or  git bisect bad
# Repeat until root cause commit is found
git bisect reset

# What's using this port?
lsof -i :PORT

# What's this process doing?
ps aux | grep PROCESS

# Watch file changes
fswatch -r ./src

# Disk space
df -h

# System resource usage
top -l 1 | head -10

© CraftOS-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/debug-pro of CraftOS-dev/CraftBot.

• SKILL.md
• .clawhub/origin.json
• _meta.json

Open the folder on GitHubat commit b50970c