capture.mjs --paginate fences spell {page} unquoted — PowerShell eats it #10

Every capture.mjs --paginate fence in the skills spells the output placeholder unquoted:

--out .gs-superadmin/tmp/audit-rules-{page}.json

Windows PowerShell consumes the braces, so the command fails until the argument is single-quoted. The surrounding prose explains that {page} is literal and the script substitutes it, one file per page — but never mentions the shell.

The project already documents this hazard class elsewhere. skills/setup/SKILL.md:188 reads:

Windows PowerShell re-parses -e strings and errors on [, || and }.

So the knowledge exists in the repo and is simply absent from the fences. Found live on Windows, on the first capture command of a fresh workspace setup.

Locations

Five skills, eight fences:

• plugins/gs-superadmin/skills/audit/SKILL.md — 2
• plugins/gs-superadmin/skills/deprecate/SKILL.md — 3
• plugins/gs-superadmin/skills/email-report/SKILL.md — 1
• plugins/gs-superadmin/skills/refresh/SKILL.md — 1
• plugins/gs-superadmin/skills/setup/SKILL.md — Phase 4

Fix

Quote the placeholder in each fence, or state the PowerShell requirement in the prose beside it. Whichever is chosen should be applied uniformly: this is one fact living in eight places, and a fix that reaches only some of them leaves the same trap for the next reader.

Verifying

Run any one of the fences verbatim in PowerShell before and after the change. Before, the file is written with the placeholder consumed; after, pagination produces one file per page as documented.

Note that npm run build and the doc gates pass either way — no CI suite executes skill prose, so this is verified by running the command, not by a green check.