How do I install the Niradler Dbga Node skill?

Run npx skillmds@latest add tomevault-io/niradler-dbga-node in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Niradler Dbga Node skill do?

Node.js / TypeScript It is listed under Coding & Dev Tools on SkillMD.

Is Niradler Dbga Node safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Niradler Dbga Node?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Niradler Dbga Node free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Niradler Dbga Node?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Niradler Dbga Node by tomevault-io — Agent Skill

Name: Niradler Dbga Node
Author: tomevault-io

File contents

Node.js / TypeScript

TypeScript-first development skill. Delivers strict-typed, clean, verified Node/TS code. JavaScript without types is the fallback, not the default.

Core stance

Strict TypeScript. strict: true with every flag on; no any without a justification; types model the domain, not the other way around.
Type inference over annotation. Annotate public API boundaries and let inference carry the rest.
Evidence first. When code crashes, hangs, or returns wrong output, gather runtime evidence with dbga and the debug-agent skill before guessing. See references/debugging.md.
Clean, self-explaining code; no comments unless asked — see _shared/clean-code.md (cross-reference, do not restate).
Audit then suggest dependency bumps (npm outdated, npm audit) — see _shared/dependency-hygiene.md.
Validation discipline — see _shared/evidence-first.md.

References — load on demand

Need	Read
Module/composition/DI patterns, anti-patterns	`references/design-patterns.md`
Advanced types: conditional, mapped, template-literal, branded, discriminated unions, `infer`, utility types	`references/typescript-types.md`
async/await, Promise combinators, concurrency limits, streams, EventEmitter, graceful shutdown	`references/async-patterns.md`
Typed errors, Result types, `never` exhaustiveness, custom error classes, async error wrapping	`references/errors-structure.md`
Plain JS with no types: JSDoc typing, defensive coding, ESM	`references/js-fallback.md`
`dbga` + vscode-js-debug recipes for Node/TS	`references/debugging.md`

Toolchain

Runtime: node (use a current LTS). Package manager: npm / pnpm.
Type-check: tsc --noEmit. Lint/format: ESLint + Prettier.
Test: Vitest (preferred) or Jest. Cover edge cases, not just the happy path.
Run a real flow (tsc --noEmit, the test suite, or the actual command) before declaring anything done.

Evidence-First Debugging (debug-agent toolkit)

You have dbga — an evidence-first debugger for Python/Go/Node over DAP — and the debug-agent skill. When code crashes, hangs, produces wrong output, or you need live runtime state, DO NOT guess from source. Gather evidence:

dbga diagnose --timeout 60 --cwd <dir> -- node buggy.js → triage a crash to the deepest user frame
dbga session start --break-at file:line -- <script> then dbga session eval --expr "<x>" → inspect live state
Invoke the debug-agent skill for the full evidence-first loop.

Node uses vscode-js-debug (set $DBGA_JS_DEBUG_SERVER if not auto-discovered); only a single launched process is validated today. Validate against real use flows and verify the fix at the original fault before declaring it done.

Source: niradler/dbga — distributed by TomeVault.

---name: niradler-dbga-nodedescription: Node.js / TypeScript---# Node.js / TypeScriptTypeScript-first development skill. Delivers strict-typed, clean, verified Node/TS code. JavaScript without types is the fallback, not the default.## Core stance- **Strict TypeScript.** `strict: true` with every flag on; no `any` without a justification; types model the domain, not the other way around.- **Type inference over annotation.** Annotate public API boundaries and let inference carry the rest.- **Evidence first.** When code crashes, hangs, or returns wrong output, gather runtime evidence with `dbga` and the `debug-agent` skill before guessing. See `references/debugging.md`.- **Clean, self-explaining code; no comments unless asked** — see `_shared/clean-code.md` (cross-reference, do not restate).- **Audit then suggest dependency bumps** (`npm outdated`, `npm audit`) — see `_shared/dependency-hygiene.md`.- **Validation discipline** — see `_shared/evidence-first.md`.## References — load on demand| Need | Read || --- | --- || Module/composition/DI patterns, anti-patterns | `references/design-patterns.md` || Advanced types: conditional, mapped, template-literal, branded, discriminated unions, `infer`, utility types | `references/typescript-types.md` || async/await, Promise combinators, concurrency limits, streams, EventEmitter, graceful shutdown | `references/async-patterns.md` || Typed errors, Result types, `never` exhaustiveness, custom error classes, async error wrapping | `references/errors-structure.md` || Plain JS with no types: JSDoc typing, defensive coding, ESM | `references/js-fallback.md` || `dbga` + vscode-js-debug recipes for Node/TS | `references/debugging.md` |## Toolchain- Runtime: `node` (use a current LTS). Package manager: npm / pnpm.- Type-check: `tsc --noEmit`. Lint/format: ESLint + Prettier.- Test: Vitest (preferred) or Jest. Cover edge cases, not just the happy path.- Run a real flow (`tsc --noEmit`, the test suite, or the actual command) before declaring anything done.## Evidence-First Debugging (debug-agent toolkit)You have `dbga` — an evidence-first debugger for Python/Go/Node over DAP — and the `debug-agent` skill. When code crashes, hangs, produces wrong output, or you need live runtime state, DO NOT guess from source. Gather evidence:- `dbga diagnose --timeout 60 --cwd <dir> -- node buggy.js` → triage a crash to the deepest user frame- `dbga session start --break-at file:line -- <script>` then `dbga session eval --expr "<x>"` → inspect live state- Invoke the `debug-agent` skill for the full evidence-first loop.Node uses vscode-js-debug (set `$DBGA_JS_DEBUG_SERVER` if not auto-discovered); only a single launched process is validated today. Validate against real use flows and verify the fix at the original fault before declaring it done.---> Source: [niradler/dbga](https://github.com/niradler/dbga) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Niradler Dbga Node