agentsclimarketplace

Windows node sandbox troubleshooting

Skill VJDiPaola/skill-forge/windows-node-sandbox-troubleshooting

A skill library for AI coding agents with a CI quality gate: 38 skills, four-target sync, and an 18-check eval harness that fails the build on malformed skills.

Install
npx -y skills add VJDiPaola/skill-forge --skill windows-node-sandbox-troubleshooting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Troubleshoot Windows-specific Node/npm issues in Codex or sandboxed agent sessions. Use when Node or npm misbehaves inside Codex or sandboxed agent sessions on Windows.

SKILL.md

1.8 KB, 396 tokens by cl100k_base, as published. Nobody here has run it

Windows Node Sandbox Troubleshooting

Use this workflow for Windows execution issues in automated or sandboxed Node workflows.

Known Patterns And Fixes

1) npm blocked by PowerShell execution policy

Symptom:

  • npm.ps1 cannot be loaded because running scripts is disabled

Fix:

  • Use npm.cmd ... instead of npm ....

2) UNC workdir fallback to C:\Windows

Symptom:

  • CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory.
  • npm ERR! enoent Could not read package.json ... C:\Windows\package.json

Fix:

  • Use a normal drive-letter path for workdir, such as C:\Users\...\repo, not \\?\....
  • This matters even if the visible current directory was supplied to the agent as a UNC-style path.

3) spawn EPERM during test or build

Symptom:

  • esbuild, vite, next, or worker process startup fails with spawn EPERM

Fix:

  • Re-run the command with the tool's elevated or unrestricted execution mode.

4) BOM corruption in JSON or TS config

Symptom:

  • Unexpected token '' in package.json or another config file

Fix:

  • Rewrite the file as UTF-8 without BOM.
  • In PowerShell, use System.Text.UTF8Encoding($false) with WriteAllText.

Recovery Order

  1. Switch to npm.cmd.
  2. Replace UNC workdir values with a normal C:\... path.
  3. Retry with elevated execution if worker startup fails.
  4. Strip BOM from recently edited config files if parsing errors remain.
  5. Re-run npm.cmd run test, npm.cmd run lint, and npm.cmd run build.

What ships with it: 2 files

421 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.