Agent skill

Node Inspect Debugger

Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

Install Node Inspect Debugger

skills CLI

$ npx skills add openclaw/openclaw --skill node-inspect-debugger -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw node-inspect-debugger --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/node-inspect-debugger .claude/skills/node-inspect-debugger && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "node-inspect-debugger" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger into .claude/skills/node-inspect-debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "node-inspect-debugger", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add openclaw/openclaw --skill node-inspect-debugger -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw node-inspect-debugger --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/node-inspect-debugger .agents/skills/node-inspect-debugger && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "node-inspect-debugger" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger into .agents/skills/node-inspect-debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "node-inspect-debugger", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add openclaw/openclaw --skill node-inspect-debugger -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw node-inspect-debugger --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/node-inspect-debugger .cursor/skills/node-inspect-debugger && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "node-inspect-debugger" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger into .cursor/skills/node-inspect-debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "node-inspect-debugger", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/openclaw/openclaw.git --path skills/node-inspect-debugger

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add openclaw/openclaw --skill node-inspect-debugger -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw node-inspect-debugger --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/node-inspect-debugger .gemini/skills/node-inspect-debugger && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "node-inspect-debugger" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger into .gemini/skills/node-inspect-debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "node-inspect-debugger", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install openclaw/openclaw node-inspect-debugger

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add openclaw/openclaw --skill node-inspect-debugger -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/node-inspect-debugger .github/skills/node-inspect-debugger && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "node-inspect-debugger" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger into .github/skills/node-inspect-debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "node-inspect-debugger", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add openclaw/openclaw --skill node-inspect-debugger -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw node-inspect-debugger --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/node-inspect-debugger .opencode/skills/node-inspect-debugger && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "node-inspect-debugger" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/node-inspect-debugger into .opencode/skills/node-inspect-debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "node-inspect-debugger", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: node-inspect-debugger
GitHub stars: 392k
Used in: 1 other repo
Token cost: ~894 tokens
SKILL.md length: 310 words
Files: 1
Skills in repo: 93
Repo updated: Oct 8, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

Tasks that involve Responsive design
Calls node, npm and curl

What it does

Node Inspect Debugger is an agent skill from openclaw/openclaw. Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Responsive design. It works with Node.js and Vitest. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

When your agent uses it

Tasks that involve Responsive design

Example prompts

“/node-inspect-debugger”

Requirements

Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 1eb5970. 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:
- node
- npm
- curl
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and curl, 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

Node Inspect Debugger loads about 894 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 310 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~27
When it runs · the whole SKILL.md, loaded when a task matches: ~894

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 openclaw/openclaw at commit 1eb5970, republished under its MIT licence (© openclaw). 310 words, ~894 tokens.

Download SKILL.mdSave it as .claude/skills/node-inspect-debugger/SKILL.md (or your agent's skills folder).

name: node-inspect-debugger
description: Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

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: OPENCLAW_VITEST_MAX_WORKERS=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 directly; Ctrl+C exits repl mode.
Exit safely: cont before quitting if the process should continue; otherwise kill.

OpenClaw tips

Prefer 127.0.0.1 inspector binds. Do not expose --inspect=0.0.0.0 unless the network is isolated.
For Vitest, debug one file with one worker. Avoid worker pools while stepping.
For TS source breakpoints, use --enable-source-maps when useful; node inspect can still show emitted paths.
For child processes, NODE_OPTIONS=--inspect-brk can propagate the inspector, but each child needs its own port.
For long-lived gateway or dev processes, attach by PID after confirming the target with /json/list.

Programmatic CDP

Install tooling outside the repo unless the project already depends on it:

bash

mkdir -p /tmp/cdp-tools
npm --prefix /tmp/cdp-tools i chrome-remote-interface
NODE_PATH=/tmp/cdp-tools/node_modules node /tmp/cdp-debug.cjs

Minimal driver:

const CDP = require("chrome-remote-interface");

(async () => {
  const client = await CDP({ port: 9229 });
  const { Debugger, Runtime } = client;

  Debugger.paused(async ({ callFrames, reason }) => {
    const top = callFrames[0];
    console.log("paused", reason, top.url, top.location.lineNumber + 1);
    const { result } = await Debugger.evaluateOnCallFrame({
      callFrameId: top.callFrameId,
      expression: "JSON.stringify({ pid: process.pid })",
    });
    console.log(result.value ?? result.description);
    await Debugger.resume();
  });

  await Runtime.enable();
  await Debugger.enable();
  await Debugger.setBreakpointByUrl({ urlRegex: ".*target\\.js$", lineNumber: 41 });
  await Runtime.runIfWaitingForDebugger();
})();

Profiles

CPU: enable Profiler, start, wait, stop, write /tmp/profile.cpuprofile, open in Chrome DevTools.
Heap: enable HeapProfiler, collect addHeapSnapshotChunk, call takeHeapSnapshot, write /tmp/heap.heapsnapshot.

Pitfalls

--inspect does not pause; use --inspect-brk when setup must happen before code runs.
Default port is 9229; use --inspect=0 or a unique port for parallel targets.
If a breakpoint misses, confirm file path, source map behavior, and whether execution already passed the line.
If the process appears frozen after detaching, it may still be paused in the debugger.

Files

Just SKILL.md in skills/node-inspect-debugger of openclaw/openclaw.

Open the folder on GitHubat commit 1eb5970

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in openclaw/openclaw, which our catalogue first saw on October 8, 2026.

Kevin100202/Rocket-Design-and-Manufacturing-Automation-Program-from-Shenzhen22highschoolskills/node-inspect-debugger

Compare with similar skills

Node Inspect Debugger next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Node Inspect Debugger compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Node Inspect Debugger this skillopenclaw/openclaw	392k	1 repos	~894	Automated safety check: Pass	MIT	today
Quasar Skilldskilld-dev/vue-ecosystem-skills	181	—	~1.6k	Automated safety check: Pass	MIT	15 days ago
Repo Healthcheck Nodecommercetools/ui-kit	154	—	~1.6k	Automated safety check: Notes	MIT	5 days ago
Browser QAaffaan-m/ECC	275k	2 repos	~1k	Automated safety check: Pass	MIT	3 days ago
OpenClaw Design Auditopenclaw/clawhub	9.5k	—	~498	Automated safety check: Pass	MIT	today
Website Responsive Validationmacalbert/envilder	138	—	~739	Automated safety check: Pass	MIT	3 days ago

Similar skills

Quasar Skilld
skilld-dev/vue-ecosystem-skills
Build, configure, and debug apps with the Quasar framework (quasar npm package, v2.33.1).
181 GitHub stars~1.6k tokensUpdated 15 days ago
Frontend & DesignAuto-check passed
Repo Healthcheck Node
commercetools/ui-kit
Verify a Node.js/TypeScript repo's development environment is correctly set up.
154 GitHub stars~1.6k tokensUpdated 5 days ago
Frontend & DesignAuto-check: notes
Browser QA
affaan-m/ECC
Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction…
275k GitHub starsUsed in 2 repos~1k tokens
Frontend & DesignAuto-check passed
OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
9.5k GitHub stars~498 tokensUpdated today
Frontend & DesignAuto-check passed
Website Responsive Validation
macalbert/envilder
Playwright-based visual validation procedure for Envilder website changes.
138 GitHub stars~739 tokensUpdated 3 days ago
Frontend & DesignAuto-check passed
Gstack
LeoYeAI/openclaw-master-skills
Fast headless browser for QA testing and site dogfooding. An agent skill from LeoYeAI/openclaw-master-skills.
2.2k GitHub stars~4.1k tokensUpdated 2 mo ago
Frontend & DesignAuto-check: notes

Questions about Node Inspect Debugger

What does Node Inspect Debugger do?

Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles. Node Inspect Debugger is an agent skill from openclaw/openclaw.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

When should I use Node Inspect Debugger?

Node Inspect Debugger fits situations like: tasks that involve Responsive design.

How do I install Node Inspect Debugger in Claude Code?

Run `npx skills add openclaw/openclaw --skill node-inspect-debugger -a claude-code`. Or copy the skill folder (skills/node-inspect-debugger in openclaw/openclaw) into .claude/skills/node-inspect-debugger in your project. Claude Code loads it when a task matches its description.

How do I install Node Inspect Debugger in Codex?

Run `npx skills add openclaw/openclaw --skill node-inspect-debugger -a codex`. Or copy the skill folder (skills/node-inspect-debugger in openclaw/openclaw) into .agents/skills/node-inspect-debugger in your project. Codex loads it when a task matches its description.

Can I use Node Inspect Debugger in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill node-inspect-debugger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/node-inspect-debugger, .gemini/skills/node-inspect-debugger, .github/skills/node-inspect-debugger and .opencode/skills/node-inspect-debugger in your project.

What does Node Inspect Debugger need to run?

Going by SKILL.md and its folder, Node Inspect Debugger needs the command-line tools its instructions call (node, npm, curl and jq). Our summary lists: Node.js.

Does Node Inspect Debugger access the network?

SKILL.md contains no URLs. Its commands use npm and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Node Inspect Debugger safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Node Inspect Debugger use?

Node Inspect Debugger is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Node Inspect Debugger use?

About 894 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Node Inspect Debugger?

Skills that share tags, products or a category with Node Inspect Debugger: Quasar Skilld (skilld-dev/vue-ecosystem-skills, 181 stars), Repo Healthcheck Node (commercetools/ui-kit, 154 stars), Browser QA (affaan-m/ECC, 275k stars) and OpenClaw Design Audit (openclaw/clawhub, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Node Inspect Debugger?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,610 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 8, 2026.

Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Node Inspect Debugger

Install Node Inspect Debugger

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Node Inspect Debugger

Files

Used in 1 other repository

Compare with similar skills

Similar skills

Quasar Skilld

Repo Healthcheck Node

Browser QA

OpenClaw Design Audit

Website Responsive Validation

Gstack

More from openclaw/openclaw

Openclaw Live Updater

Tmux

Feishu Doc

Openclaw PR Maintainer

Browser Automation

Clawsweeper

Questions about Node Inspect Debugger

Install Node Inspect Debugger

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Node Inspect Debugger

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from openclaw/openclaw

Related

Questions about Node Inspect Debugger