Skip to content

docs(skill-inspector): document the Windows stdout form for scan reports #1017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bharathvemula wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs(skill-inspector): document the Windows stdout form for scan reports #1017

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
38e1bb8
docs(skill-inspector): document the Windows stdout form for scan reports
bharathvemula Nov 4, 2026
e554641
docs(skill-inspector): write the Windows report with -LiteralPath
bharathvemula Nov 6, 2026
5eb23f7
docs(skill-inspector): use BOM-free WriteAllText for Windows report
bharathvemula Nov 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion skills/skill-inspector/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,11 +36,28 @@ Do not rely on the numeric score alone. A low score can miss semantic risk, and

2. Run the static scan.

On POSIX systems:

```bash
skillspector scan "$TARGET" --no-llm --format json --output /tmp/skill-inspector-report.json
```

If the command exits non-zero, inspect any partial report and continue manually. Record that the static line was incomplete.
On Windows, safe file output is unsupported, so `--output` always fails
(exit code 2) and no report is written. Omit `--output` and redirect
stdout to a file outside the scan target instead. Use
`[IO.File]::WriteAllText(...)`, not `>` or `Set-Content -Encoding utf8`:
plain `>` writes UTF-16 JSON on PowerShell 5.1, which JSON parsers
reject, and `Set-Content -Encoding utf8` writes a UTF-8 BOM on
PowerShell 5.1, which Python and Node JSON parsers also reject. The
`[IO.File]::WriteAllText(...)` form is BOM-free on both PowerShell 5.1
and 7+ (`-Encoding utf8NoBOM` is an alternative, but only on
PowerShell 6+):

```powershell
[IO.File]::WriteAllText("$env:TEMP\skill-inspector-report.json", ((skillspector scan "$TARGET" --no-llm --format json) -join "`n"))
```

If the command exits non-zero, inspect any partial report and continue manually. Record that the static line was incomplete. On Windows, a non-zero exit from a command using `--output` is a platform refusal, not a scan failure: no partial report exists, so do not look for one or retry the same command.

3. Read the SkillSpector report.

Expand Down
Loading