CtrlK
BlogDocsLog inGet started
Tessl Logo

node-inspect-debugger

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

57

Quality

68%

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/software-development/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.

The content is a highly actionable, well-structured debugging reference with runnable code, numbered workflows, a pitfalls section, and a verification checklist. The main gap is that validation checkpoints live in a separate checklist rather than being embedded directly in each multi-step workflow.

DimensionReasoningScore

Conciseness

The body is a lean technical reference of commands, a REPL table, and runnable code; it assumes Claude's competence and avoids explaining basics, with only minor open prose that could be trimmed.

4 / 5

Actionability

Guidance is fully executable: copy-paste launch commands, a complete CDP driver script, a command-reference table, and one-shot recipes covering the common cases.

5 / 5

Workflow Clarity

Multi-step attach and TUI-debug flows use explicit numbered sequences, and a verification checklist plus a pitfalls section provide error-recovery guidance, but validation checkpoints are not embedded inline within the workflows.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly headed sections with no nested references; with no bundle files present, structure is good, though the skill exceeds 50 lines so the simple-skill exemption to a 5 does not apply.

4 / 5

Total

17

/

20

Passed

Description

53%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.

The description is a concise, third-person statement of a clear niche, but it states only the 'what' and omits any 'when to use' trigger guidance. Adding a 'Use when...' clause with natural trigger phrases would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when a Node test fails and you need to inspect intermediate state, walk the call stack, or set breakpoints beyond console.log.'

Include a few natural trigger phrases or file/extension cues (e.g. 'Node.js', '.js/.ts scripts', 'breakpoints', 'CPU profile', 'heap snapshot') to broaden trigger-term coverage.

Optionally surface 1-2 concrete capabilities (breakpoints, stepping, scope dumps) in the description for fuller specificity.

DimensionReasoningScore

Specificity

Names the domain (Node.js debugging) and two concrete tools ('--inspect', 'Chrome DevTools Protocol CLI'), but lists no specific actions like breakpoints, stepping, or profiling, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Debug Node.js' is a natural phrase users would say, but 'Chrome DevTools Protocol CLI' is jargon and common synonyms/variations are missing.

3 / 5

Distinctiveness Conflict Risk

The Node.js inspect/CDP niche is clearly distinct with minimal conflict risk; only minor overlap with related general debugging skills.

4 / 5

Total

13

/

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.

Validation13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.