Debugging tools

Skill S3YED/appie-kit/skills/fleet/debugging-tools

Build Your Own AI Employee. The complete starter kit for OpenClaw + Hermes Agent. 155 deduplicated skills, drag-and-drop workspace, case studies, install scripts.

Install

npx -y skills add S3YED/appie-kit --skill debugging-tools

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Debugging tools for development: pdb, debugpy, and Node.js inspect debugger.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 452 tokens by cl100k_base, as published. Nobody here has run it

Debugging Tools

Debugging tools for stepping through code, inspecting state, and diagnosing runtime issues. This umbrella covers the two main ecosystems: Python and Node.js.

When to Use Debugger Tools

Tool	When
`breakpoint()` + pdb	Local, interactive, simplest. Add `breakpoint()` in source, run normally.
`python -m pdb`	Launch existing script under pdb with no source edits.
`debugpy`	Remote / headless / attach to already-running process. Talks DAP.
`node inspect`	Node.js built-in inspector. Zero install, CLI REPL.
`ndb` / CDP	Scriptable from Node/Python; automate many breakpoints across runs.

Start with breakpoint() or node inspect. These are the cheapest things that work.

Don't Use Debugger For

Things print() / console.log / pytest -vv --tb=long solve in under a minute. Breakpoint-driven debugging is heavier; use it when the payoff is real.

Quick Reference: pdb

Inside any pdb prompt ((Pdb)):

n(ext)     — Execute next line
s(tep)     — Step into function
c(ontinue) — Continue until breakpoint
l(ist)     — Show source around current line
p <expr>   — Print expression value
pp <expr>  — Pretty-print expression
b <line_no> — Set breakpoint at line

Quick Reference: node inspect

n            — Next
s            — Step into
o            — Step out
cont         — Continue
list(n)      — List source around line
repl         — Enter REPL mode to eval expressions
watch('var') — Watch expression across steps

Reference Files

references/python-debugpy.md — Full pdb + debugpy reference (breakpoint(), remote attach, DAP)
references/node-inspect-debugger.md — Full Node.js --inspect reference (CDP, breakpoints, heap snapshots)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.