CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

node-inspect-debugger

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

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/node-inspect-debugger/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference: nearly every line is an executable command or a non-obvious pitfall, and it is organized into clear scenario-based sections. Its only real weaknesses are mild redundancy with Node's documented REPL basics and content (the CDP driver, profile recipes) that is large enough to justify splitting into bundle files.

Suggestions

Trim or condense the basic REPL command list (cont/next/step/bt) to only the non-obvious entries, keeping commands like sb('functionName') and the repl-mode locals trick that Claude is less likely to recall.

Move the CDP minimal driver and the heap/CPU profile capture recipes into scripts/ or references/ files, referenced one level deep from a short Programmatic CDP section, to keep SKILL.md as an overview.

Convert the Pitfalls list into explicit validate-then-proceed checkpoints inside the debugging flows (e.g., verify /json/list shows the target before attaching) to strengthen feedback loops.

DimensionReasoningScore

Conciseness

The body is lean — bullet commands, a compact CDP driver, and high-value pitfalls with no padded prose. Minor trimmable content remains, such as the basic REPL command list ("cont, next, step, out, pause") and "bt"/"list(8)" which are standard documented node inspect commands Claude largely already knows.

4 / 5

Actionability

Everything is copy-paste ready: exact invocations ("node inspect path/to/script.js", "node --inspect-brk --import tsx ...", "kill -SIGUSR1 <pid>"), a curl/jq inspection command, and a complete executable CDP driver covering breakpoint, evaluate, and resume flows.

5 / 5

Workflow Clarity

Scenarios are clearly sequenced: quick-start entry points, REPL controls with an explicit safety checkpoint ("cont before quitting if the process should continue; otherwise kill"), a staged CDP path (install tooling → driver → profiles), and pitfall-recovery guidance ("If a breakpoint misses, confirm file path, source map behavior..."). It is a reference-style skill rather than a multi-step pipeline, so feedback loops are present but informal rather than explicit validate-then-proceed steps.

4 / 5

Progressive Disclosure

No bundle files exist and the body references none; sections are well-organized (Quick start, Debugger REPL, OpenClaw tips, Programmatic CDP, Profiles, Pitfalls) and easy to navigate. At ~70 lines it exceeds the under-50-line exception for a clean 5, and the ~25-line CDP driver plus profile recipes are arguably large enough to live in a scripts/ or references/ file, matching anchor 4's "minor organization gaps".

4 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A terse, specific description that clearly names the domain and its concrete capabilities without fluff. Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness and leaves invocation conditions implicit.

Suggestions

Add a 'when' clause, e.g. "Use when a Node.js process hangs, leaks memory, has hidden locals or flaky tests, or when stepping through TypeScript or child processes is needed."

Add one or two natural synonyms users would say, such as "step through", "memory leak", or "profiling", to broaden trigger coverage.

State capabilities as actions (e.g., "Set breakpoints, capture heap snapshots and CPU profiles") rather than a bare list of nouns after a single verb.

DimensionReasoningScore

Specificity

The description lists several specific capabilities — "node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles" — but the only verb is "Debug", so it enumerates tools/topics more than actions, leaving minor gaps versus the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clear (debugging Node.js via inspector, breakpoints, CDP, heap/CPU profiles), but there is no "Use when..." or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Debug Node.js", "breakpoints", "heap", "CPU profiles", "node inspect" — phrases a user would plausibly say. A few common variations are missing (e.g., "step through", "memory leak", "profiling"), keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Node.js inspector-based debugging) with distinctive terms like "node inspect", "--inspect", and "heap"/"CPU profiles"; minor overlap risk remains with closely related skills (general JavaScript debugging or Chrome DevTools/CDP skills), matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

openclaw/openclaw

Path

skills/node-inspect-debugger/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.