ps-test 100/100 — SaferSkills

Is ps-test safe to install?

SaferSkills independently audited ps-test (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/ps-test/SKILL.md · 1 file

.claude/skills/ps-test/SKILL.md1.8 KB · Markdown

name: ps-test

description: Test a PowerShell script directly from WSL2. Runs a script with given parameters and shows structured output. Use during PS script development to verify behavior without going through the full MCP stack.

argument-hint: "<script-name> [params]"

allowed-tools: Bash(powershell.exe *), Bash(echo *), Read, Glob

model: haiku

Test PowerShell Script

Run a PowerShell script from WSL2 and show structured output.

Usage

/ps-test screenshot -WindowTitle "Notepad"
/ps-test see -ProcessName "chrome"
/ps-test list-windows
/ps-test clipboard -Action read
/ps-test processes -Name "node" -Limit 5

Steps

Resolve the script path. Scripts live in scripts/ — find the matching file:

   ls /home/flowing1978/projects/a-eyes/scripts/

Convert to Windows UNC path: \\wsl.localhost\Ubuntu\home\flowing1978\projects\a-eyes\scripts\<name>.ps1

Build the PowerShell command from $ARGUMENTS:

First token = script name (without .ps1)
Remaining tokens = parameters passed as-is

Run the script:

   powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass \
     -File "\\wsl.localhost\Ubuntu\home\flowing1978\projects\a-eyes\scripts\<name>.ps1" \
     <params>

Show output:

If valid JSON: pretty-print with key highlights
If error: show stderr and suggest likely cause
Show exit code

For image results (base64 data field): show field size in KB instead of full base64.

Common Issues

$PID variable not writable → script uses $PID instead of $wpid — report as bug
Execution policy errors → add -ExecutionPolicy Bypass
Empty output → check stderr for PowerShell load errors
Access denied → window may require elevated permissions or be a protected process

ps-test— agent skill

Is ps-test safe to install?

Test PowerShell Script

Usage

Steps

Common Issues

Audit the pieces. Scan the whole. Decide.