Test results
Windows Background Script Review for Node.js: test results
Tested 2026-11-22, skill version 1.0.1 at the time of loading this page. We run every skill on a strong and a weak model before it is listed, and publish both verdicts, including where the weak one fails.
Verdicts
- Date
- 2026-11-22
- Strong · claude-sonnet-5-5 (Claude Code alias "sonnet")
- Right on all 12 inputs on the 1.0.1 bytes, read by hand. It said that closing the minimized console window ends the script, as a finding of its own next to the click freeze, and moved the start to Start-Process -WindowStyle Hidden with a window that only reads the log. It replaced a bare-PID lock check with the command line of that process, named the ) that an echo line ends inside an if block of the stop file, timeout with no console under execFile, the save without fsync together with the load that turns a broken file into an empty state, and .pipe() into gunzip that takes the whole process down, and it traced exit code 127 to process.exit() after fetch. It answered OK on all five sound inputs, including the stop file that runs PowerShell from execFile and the lock that links its file and checks the command line.
- Weak · claude-haiku-5-5 (Claude Code alias "haiku")
- Right on 10 of 12 on the 1.0.1 bytes, read by hand. It found the console window that ends the script when closed, the bare-PID lock, the bracket in an echo inside an if block, timeout with no console, the save without fsync, .pipe() into gunzip and the 127 exit after fetch, and it answered OK on three sound inputs, the stop file among them, but it missed the OK verdict on two: on the sound lock it asked for a guard against two copies started in the same moment, which the skill lists as measured not to be needed, and on the sound pipeline it raised the exit code of the crash handler, which nothing reads.
With and without the skill
Tested 2026-11-22.
| Sonnet | Haiku | |||
|---|---|---|---|---|
| with | without | with | without | |
| Inputs judged right (12 inputs) | 12/12 | 8/12 | 10/12 | 5/12 |
Same request on both sides, scored on the point in any words. Read by hand, Sonnet without the skill already knew the .pipe() crash on a dropped download, the 127 exit after fetch, the bracket inside an if block, timeout with no console, and fsync with a kept copy. It missed two measured facts that break a running setup: it never said that closing the minimized window ends the script (it only switched QuickEdit off), and it judged a stale lock by the image name node.exe instead of the command line. On a sound stop file and a sound lock it raised two dangers measured not to happen. Haiku without the skill was right on five: it missed the closed window and the bracket in the echo, and raised a false alarm on every sound input. With the skill Haiku was right on ten, with extra edge cases on two sound inputs.
Same cases and the same checks with and without the skill. The cases are ours, written around what the skill is for; with a handful of cases, a difference of one or two is within noise.
Note
Twelve inputs written by us: seven with a planted Windows fault or a symptom (a start file that runs node in a minimized window and logs to the console, a stop file with a bracket in an echo inside an if block, the same stop file waiting with timeout while a Node panel runs it through execFile, a lock that trusts a live PID, a state save without fsync that reads a broken file as empty, a gzip download joined with .pipe(), and a question about exit code 127 after fetch) and five sound twins of them. Code scores every answer, and both sides get an identical request and identical checks: the verdict line, and for each fault the point in any words (closing the window ends the script, the click freeze, a start with no window, the command line of the PID, fsync and a kept copy, pipeline, process.exitCode). Re-checked on this PC on 2026-11-22 (Windows 11, Node 24): .pipe() into gunzip ends the process on a dropped connection while pipeline hands the error to the catch, process.exit() after fetch to an https host gives 127, a ) at the end of an echo line within an if block stops the .cmd, timeout refuses with no console on its input, process.kill(pid, 0) succeeds on another program's process, the command-line query takes about half a second, a powershell -Command child from execFile returns normally, and a freshly removed file name can be reused at once by linkSync. Owner-measured in October 2026 and not re-checked: the click freeze, the end of the script when its window was closed, and the broken file after a power cut without fsync. Checks widened after the runs, for both sides: the lock fix also takes a lock written before the current boot, and the window check takes the window named in one sentence and closed as 'it' in the next. Two sound inputs (the lock and the state save) had real gaps found by bare Sonnet and were fixed and re-run before scoring. The first wording of the skill was run once (Sonnet 11 of 12, Haiku 9 of 12): a code for a .cmd that had not been run yet turned a sound start file into a change request for Sonnet. That code was removed, the closed-window rule was split out as a finding of its own, and the skill side was re-run in full on all 12 inputs. The bare side is unchanged. One run per model and input. The side with the skill was run once more in full on the final bytes, after two command lines were reshaped for the catalog safety gate: Sonnet 12 of 12 again, Haiku 9 of 12 (10 of 12 the run before; one run per model and setup). Version 1.0.1, 22 November 2026: two sentences were reworded so that no published post on our blog shares a run of five words with the file; the side with the skill was run again in full on those bytes: Sonnet 12 of 12, Haiku 10 of 12. The side without the skill is unchanged.
What was not measured
- Models other than the two named above were not run.
- Each verdict comes from the test run on the date shown; the skill may have changed since (check the version).
- Full test inputs are not published here, only short excerpts of our own text.
- Results on your own texts, languages and domains can differ.
Back to Windows Background Script Review for Node.js · Card (JSON)