How do I install the Okojo Node Ink Debug skill?

Run npx skillmds@latest add tomevault-io/okojo-node-ink-debug 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.

Is Okojo Node Ink Debug 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 Okojo Node Ink Debug?

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 Okojo Node Ink Debug free to use?

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

Who published Okojo Node Ink Debug?

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

Okojo Node Ink Debug by tomevault-io

Name: Okojo Node Ink Debug
Author: tomevault-io

Okojo Node Ink Debug

Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox. Use this for Ink bring-up, reduced Okojo.Node repros, CommonJS/ESM/runtime compatibility debugging, debugger/disassembly investigation, and focused regression-driven fixes. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Okojo.Node Ink Debug

Use this skill for work under:

sandbox\OkojoInkProbe
sandbox\OkojoNodeDebugSandbox
src\Okojo.Node
src\Okojo
tests\Okojo.Node.Tests
docs\PALE_NODE_INK_DEBUG_WORKFLOW.md

Primary goal

Move sandbox\OkojoInkProbe forward by fixing real engine/runtime/compiler bugs and missing compatibility surfaces in a disciplined order.

Prefer:

correctness
observability/tooling
focused compatibility increments
measured optimization

Core policy

Do not treat large-app failures as app-specific until reduction proves they are.

Prefer:

Node as the reference for Node-facing behavior
V8 / Node bytecode behavior when the failure looks compiler/VM related

Avoid:

broad speculative fixes
Ink-specific hacks for general runtime/compiler bugs
skipping the reduction step when a smaller repro is possible

Required workflow

reproduce in sandbox\OkojoInkProbe
reduce to the smallest JS shape possible
move the reduced shape into tests\Okojo.Node.Tests when stable
inspect disassembly / debugger state in sandbox\OkojoNodeDebugSandbox
compare with Node behavior
implement the narrow fix
rerun focused regressions
rerun Ink to reveal the next blocker

Read:

docs\PALE_NODE_INK_DEBUG_WORKFLOW.md

before doing substantial work in this area.

Required tools

Real integration checkpoint

dotnet run --project sandbox\OkojoInkProbe\OkojoInkProbe.csproj -c Release -- --debugger

Focused debugger sandbox

dotnet run --project sandbox\OkojoNodeDebugSandbox\OkojoNodeDebugSandbox.csproj -c Release -- --app-root <appRoot> --entry <entry> --stop caught --log <logPath>

Use the focused debugger sandbox for:

debugger; stops
caught exceptions
disassembly around the current PC
locals/register inspection
reduced app repros

Testing loop

Focused loop:

dotnet test tests\Okojo.Node.Tests\Okojo.Node.Tests.csproj -c Release --filter <Name>

After a fix, rerun nearby focused regressions before going back to Ink.

If the change becomes broad or touches shared compiler/runtime paths, expand validation appropriately.

Current known lessons

the old Ink require(undefined) failure was actually a wide-register compiler bug
dedicated debugger/disassembly tooling was necessary to prove the root cause
AbortController support may be needed tactically for bring-up, but Abort* / Event* likely belong long-term in Okojo.WebPlatform / shared web globals

Deliverables expected from this skill

When using this skill, aim to leave behind:

a reduced repro
a focused regression test
a narrow code fix
a rerun of Ink showing either success or the next blocker

If the blocker changes, update the workflow note or the active session plan so other agents can resume cleanly.

Source: akeit0/okojo — distributed by TomeVault.

---name: okojo-node-ink-debugdescription: Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox. Use this for Ink bring-up, reduced Okojo.Node repros, CommonJS/ESM/runtime compatibility debugging, debugger/disassembly investigation, and focused regression-driven fixes. Use when this capability is needed.---# Okojo.Node Ink DebugUse this skill for work under:- `sandbox\OkojoInkProbe`- `sandbox\OkojoNodeDebugSandbox`- `src\Okojo.Node`- `src\Okojo`- `tests\Okojo.Node.Tests`- `docs\PALE_NODE_INK_DEBUG_WORKFLOW.md`## Primary goalMove `sandbox\OkojoInkProbe` forward by fixing real engine/runtime/compiler bugs and missing compatibility surfaces in a disciplined order.Prefer:1. correctness2. observability/tooling3. focused compatibility increments4. measured optimization## Core policyDo not treat large-app failures as app-specific until reduction proves they are.Prefer:- Node as the reference for Node-facing behavior- V8 / Node bytecode behavior when the failure looks compiler/VM relatedAvoid:- broad speculative fixes- Ink-specific hacks for general runtime/compiler bugs- skipping the reduction step when a smaller repro is possible## Required workflow1. reproduce in `sandbox\OkojoInkProbe`2. reduce to the smallest JS shape possible3. move the reduced shape into `tests\Okojo.Node.Tests` when stable4. inspect disassembly / debugger state in `sandbox\OkojoNodeDebugSandbox`5. compare with Node behavior6. implement the narrow fix7. rerun focused regressions8. rerun Ink to reveal the next blockerRead:- `docs\PALE_NODE_INK_DEBUG_WORKFLOW.md`before doing substantial work in this area.## Required tools### Real integration checkpoint```powershelldotnet run --project sandbox\OkojoInkProbe\OkojoInkProbe.csproj -c Release -- --debugger```### Focused debugger sandbox```powershelldotnet run --project sandbox\OkojoNodeDebugSandbox\OkojoNodeDebugSandbox.csproj -c Release -- --app-root <appRoot> --entry <entry> --stop caught --log <logPath>```Use the focused debugger sandbox for:- `debugger;` stops- caught exceptions- disassembly around the current PC- locals/register inspection- reduced app repros## Testing loopFocused loop:```powershelldotnet test tests\Okojo.Node.Tests\Okojo.Node.Tests.csproj -c Release --filter <Name>```After a fix, rerun nearby focused regressions before going back to Ink.If the change becomes broad or touches shared compiler/runtime paths, expand validation appropriately.## Current known lessons- the old Ink `require(undefined)` failure was actually a wide-register compiler bug- dedicated debugger/disassembly tooling was necessary to prove the root cause- `AbortController` support may be needed tactically for bring-up, but `Abort*` / `Event*` likely belong long-term in `Okojo.WebPlatform` / shared web globals## Deliverables expected from this skillWhen using this skill, aim to leave behind:- a reduced repro- a focused regression test- a narrow code fix- a rerun of Ink showing either success or the next blockerIf the blocker changes, update the workflow note or the active session plan so other agents can resume cleanly.---> Source: [akeit0/okojo](https://github.com/akeit0/okojo) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions