node-inspect-debugger Skill
Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles. Published by openclaw in openclaw.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
OpenClaw
Shell access
Copy skill directory
2 months ago · NOASSERTION license
Access note: Shell access.
How to use node-inspect-debugger Skill
Compatible clients
What is node-inspect-debugger Skill?
Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles. Published by openclaw in openclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Declared skill metadata
- Source file: skills/node-inspect-debugger/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Works with OpenClaw
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use node-inspect-debugger Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: openclaw
- Repository: openclaw/openclaw
- Skill file: skills/node-inspect-debugger/SKILL.md
What it does
Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
Skill instructions
Node Inspect Debugger Use for Node.js debugging that needs inspector access: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths. Default to node inspect first. Use Chrome DevTools Protocol only when you need scripted breakpoints, automated state capture, heap snapshots, or CPU profiles. Quick start - Pause on entry: node inspect path/to/script.js - TypeScript: node --inspect-brk --import tsx path/to/script.ts - Existing PID: kill -SIGUSR1 <pid then node inspect -p <pid - Inspect target list: curl -s http://127.0.0.1:9229/json/list | jq - OpenClaw CLI path: node --inspect-brk openclaw.mjs ... - OpenClaw test path: OPENCLAWVITESTMAXWORKERS=1 node --inspect-brk scripts/run-vitest.mjs <file Debugger REPL - Continue/step: cont, next, step, out, pause - Breakpoints: sb('file.js', 42), sb(42), sb('functionName'), breakpoints, cb('file.js', 42) - Inspect: bt, list(8), watch('expr'), exec expr - Current scope: repl, then evaluate locals dire
Verified compatibility and discovery
Frequently asked questions
What is node-inspect-debugger?
node-inspect-debugger is a open-source AI agent skill for OpenClaw with Copy skill directory. Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
Who is node-inspect-debugger best for?
node-inspect-debugger is best for reusing agent instructions, scripts, and references, testing workflows, openclaw users.
How do I install node-inspect-debugger?
Install or run node-inspect-debugger using Copy skill directory. Check node-inspect-debugger for the latest setup command.
Is node-inspect-debugger actively maintained?
node-inspect-debugger may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
