Agent skill

Node Inspect Debugger

Debug Node.js via --inspect + Chrome DevTools Protocol. An agent skill from HezaoHezao/poirot.

MITAuto-check passedTesting & QA

Install Node Inspect Debugger

skills CLI

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

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

GitHub CLI

$ gh skill install HezaoHezao/poirot 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/HezaoHezao/poirot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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 HezaoHezao/poirot --skill node-inspect-debugger -a codex

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

GitHub CLI

$ gh skill install HezaoHezao/poirot 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/HezaoHezao/poirot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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 HezaoHezao/poirot --skill node-inspect-debugger -a cursor

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

GitHub CLI

$ gh skill install HezaoHezao/poirot 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/HezaoHezao/poirot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot.git --path poirot/backend/agents/skill/builtin_skills/software-development/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 HezaoHezao/poirot --skill node-inspect-debugger -a gemini-cli

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

GitHub CLI

$ gh skill install HezaoHezao/poirot 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/HezaoHezao/poirot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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 HezaoHezao/poirot 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 HezaoHezao/poirot --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/HezaoHezao/poirot.git skills-src && mkdir -p .github/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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 HezaoHezao/poirot --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 HezaoHezao/poirot 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/HezaoHezao/poirot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/software-development/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/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/software-development/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: 250
Token cost: ~898 tokens
SKILL.md length: 241 words
Files: 1
Skills in repo: 23
Repo updated: Jul 28, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Debug Node.js via --inspect + Chrome DevTools Protocol. An agent skill from HezaoHezao/poirot.

Tasks that involve Browser testing
SKILL.md covers Overview, When to Use, Quick Reference: node inspect… and Scriptable CDP via…, plus 3 more sections
Calls node and npm

What it does

Node Inspect Debugger is an agent skill from HezaoHezao/poirot. Debug Node.js via --inspect + Chrome DevTools Protocol.

Its SKILL.md is about 900 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 Testing & QA, covering Browser testing. It works with Node.js and Chrome DevTools. The repository describes itself as: Poirot is a deep research agent kernel built for those who care about how agents are architected. The licence is MIT.

When your agent uses it

Tasks that involve Browser testing

Example prompts

“/node-inspect-debugger”

Requirements

Node.js
Pre-approved tools (allowed-tools): bash, read_file

What it can do on your machine

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

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- bash
- read_file
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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

Node Inspect Debugger loads about 898 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 241 words of instructions outside code blocks.

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

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 HezaoHezao/poirot at commit 86bf279, republished under its MIT licence (© HezaoHezao). 241 words, ~898 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 via --inspect + Chrome DevTools Protocol.
allowed-tools: bash, read_file
enabled: true
related-skills: systematic-debugging, python-debugpy
license: MIT
author: Adapted from hermes-agent (Nous Research, MIT)

Node.js Inspect Debugger

Overview

When console.log isn't enough, drive Node's built-in V8 inspector programmatically from the terminal. Real breakpoints, step in/over/out, call-stack walking, scope dumps, and arbitrary expression evaluation.

Prefer node inspect first. It's always available and the REPL is fast.

When to Use

A Node test fails and you need to see intermediate state
A Node process crashes or behaves wrong and you want to inspect state
You need to inspect a value in a closure that console.log can't reach
Perf: attach to a running process to capture a CPU profile or heap snapshot

Don't use for: things console.log solves in under a minute.

Quick Reference: `node inspect` REPL

Launch paused on first line:

bash

node inspect path/to/script.js
# or with tsx
node --inspect-brk $(which tsx) path/to/script.ts

The debug> prompt accepts:

Command	Action
`c`	continue
`n`	next line (step over)
`s`	step into
`o`	step out
`sb('file.js', line)`	set breakpoint
`cb('file.js', line)`	clear breakpoint
`watch('expr')`	watch expression
`exec('expr')`	evaluate in paused frame
`backtrace` / `bt`	show call stack
`list(N)`	show N lines around current

Scriptable CDP via chrome-remote-interface

For automated debugging (many breakpoints, collect state across runs):

bash

# Install
npm install chrome-remote-interface

# Launch node with inspect
node --inspect-brk=9229 path/to/script.js &

# Attach via script
node -e "
const CDP = require('chrome-remote-interface');
(async () => {
  const client = await CDP({port: 9229});
  const {Debugger, Runtime} = client;
  await Debugger.enable();
  await Runtime.enable();
  Debugger.paused(({callFrames}) => {
    console.log('Paused at:', callFrames[0].location);
    // Inspect scope, evaluate expressions, etc.
  });
  // Set breakpoint
  await Debugger.setBreakpointByUrl({lineNumber: 10, url: 'file:///path/to/script.js'});
  await Debugger.resume();
})();
"

Attaching to a Running Process

bash

# Start with --inspect (no brk = doesn't pause on start)
node --inspect=9229 path/to/server.js

# Attach from another terminal
node inspect localhost:9229

CPU Profile

bash

# Start with inspect
node --inspect path/to/script.js

# In another terminal, capture profile
node -e "
const CDP = require('chrome-remote-interface');
(async () => {
  const client = await CDP({port: 9229});
  const {Profiler} = client;
  await Profiler.enable();
  await Profiler.start();
  // Wait for workload...
  await new Promise(r => setTimeout(r, 10000));
  const {profile} = await Profiler.stop();
  require('fs').writeFileSync('profile.cpuprofile', JSON.stringify(profile));
})();
"

# Load profile.cpuprofile in Chrome DevTools > Performance

Pitfalls

--inspect vs --inspect-brk: --inspect doesn't pause; --inspect-brk pauses on first line. Use brk when you need to catch early code.
Port conflicts: default port 9229 may be taken. Use --inspect=9230.
ESM vs CJS: node inspect works with both, but ESM may show different call stack formatting.
Source maps: TypeScript/tsx may show transpiled line numbers. Use --enable-source-maps for accurate mapping.

Files

Just SKILL.md in poirot/backend/agents/skill/builtin_skills/software-development/node-inspect-debugger of HezaoHezao/poirot.

Open the folder on GitHubat commit 86bf279

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 skillHezaoHezao/poirot	250	—	~898	Automated safety check: Pass	MIT	2 mo ago
Prismer Node Inspect DebuggerPrismer-AI/PrismerCloud	1.6k	3 repos	~3k	Automated safety check: Pass	MIT	8 days ago
Nix Chrome Devtools MCPsrid/emanote	963	1 repos	~271	Automated safety check: Pass	Custom licence	2 mo ago
Browser Testing with Chrome DevToolsaddyosmani/agent-skills	103k	4 repos	~3.5k	Automated safety check: Warn	MIT	5 days ago
Browsingobra/superpowers-chrome	356	1 repos	~8k	Automated safety check: Pass	MIT	yesterday
Chrome Devtools Axilayer5io/sistent	138	2 repos	~989	Automated safety check: Pass	Apache-2.0	6 days ago

Similar skills

Prismer Node Inspect Debugger
Prismer-AI/PrismerCloud
Debug Node.js via --inspect + Chrome DevTools Protocol CLI. An agent skill from Prismer-AI/PrismerCloud.
1.6k GitHub starsUsed in 3 repos~3k tokens
Testing & QAAuto-check passed
Nix Chrome Devtools MCP
srid/emanote
chrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix.
963 GitHub starsUsed in 1 repo~271 tokens
Testing & QAAuto-check passed
Browser Testing with Chrome DevTools
addyosmani/agent-skills
Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.
103k GitHub starsUsed in 4 repos~3.5k tokens
Testing & QAAuto-check: warnings
Browsing
obra/superpowers-chrome
A skill your agent uses when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content…
356 GitHub starsUsed in 1 repo~8k tokens
Testing & QAAuto-check passed
Chrome Devtools Axi
layer5io/sistent
Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance.
138 GitHub starsUsed in 2 repos~989 tokens
Testing & QAAuto-check passed
Idleon Live Cdp
MrJoiny/Idleon-Injector
Inspect and interact with a running Legends of Idleon session through the Chrome DevTools Protocol on port 32123.
112 GitHub stars~1.2k tokensUpdated 4 days ago
Testing & QAAuto-check passed

Questions about Node Inspect Debugger

What does Node Inspect Debugger do?

Debug Node.js via --inspect + Chrome DevTools Protocol. An agent skill from HezaoHezao/poirot. Node Inspect Debugger is an agent skill from HezaoHezao/poirot.js via --inspect + Chrome DevTools Protocol.

When should I use Node Inspect Debugger?

Node Inspect Debugger fits situations like: tasks that involve Browser testing.

How do I install Node Inspect Debugger in Claude Code?

Run `npx skills add HezaoHezao/poirot --skill node-inspect-debugger -a claude-code`. Or copy the skill folder (poirot/backend/agents/skill/builtin_skills/software-development/node-inspect-debugger in HezaoHezao/poirot) 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 HezaoHezao/poirot --skill node-inspect-debugger -a codex`. Or copy the skill folder (poirot/backend/agents/skill/builtin_skills/software-development/node-inspect-debugger in HezaoHezao/poirot) 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 HezaoHezao/poirot --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 and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: bash, read_file.

Does Node Inspect Debugger access the network?

SKILL.md contains no URLs. Its commands use npm, 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 (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Node Inspect Debugger use?

About 898 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: Prismer Node Inspect Debugger (Prismer-AI/PrismerCloud, 1.6k stars), Nix Chrome Devtools MCP (srid/emanote, 963 stars), Browser Testing with Chrome DevTools (addyosmani/agent-skills, 103k stars) and Browsing (obra/superpowers-chrome, 356 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?

HezaoHezao (a GitHub user) maintains it in HezaoHezao/poirot, which has 250 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on July 28, 2026.

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

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.js Inspect Debugger

Overview

When to Use

Quick Reference: node inspect REPL

Scriptable CDP via chrome-remote-interface

Attaching to a Running Process

CPU Profile

Pitfalls

Files

Compare with similar skills

Similar skills

More from HezaoHezao/poirot

Related

Questions about Node Inspect Debugger

Quick Reference: `node inspect` REPL