PC Master

WarnAudited by ClawScan on May 10, 2026.

Overview

PC Master is transparent about controlling Windows from WSL2, but it gives the agent broad raw Windows command, process, file, and screenshot authority without clear guardrails.

Install only if you intentionally want the agent to control your Windows host from WSL2. Before using it, set expectations that screenshots, file operations, process kills, and arbitrary PowerShell/cmd commands require explicit confirmation and narrow targets.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If invoked too broadly, the agent could run unintended Windows commands, affect running applications, access files, or capture screen contents.

Why it was flagged

The skill's scope is open-ended host control rather than a narrow workflow, and the artifact does not add approval, allowlist, path limits, or rollback guidance for high-impact actions.

Skill content
Control the Windows PC from WSL2... manage processes... manage files on Windows... automate tasks, or do anything that requires interacting with the Windows host from WSL2
Recommendation

Use only for explicit user-requested PC-control tasks; require confirmation before destructive or broad actions, and restrict commands to named apps, files, and paths.

What this means

A mistaken or over-broad process kill could lose unsaved work, interrupt downloads, terminate meetings, or disrupt other desktop activity.

Why it was flagged

The examples use forceful process termination, which can close applications without saving work or preserving session state, and they do not instruct the agent to prefer graceful close or ask for confirmation.

Skill content
taskkill.exe /F /IM chrome.exe ... taskkill.exe /F /PID 1234
Recommendation

List matching processes first, confirm the exact target with the user, and prefer graceful close methods before using taskkill /F.

What this means

Generated PowerShell or cmd commands will run locally with the user's permissions and could change the system if the command is unsafe.

Why it was flagged

The skill instructs the agent to execute local PowerShell commands. This is expected for the stated purpose, but it is powerful local code execution.

Skill content
PS=/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe; $PS -NonInteractive -Command "Get-Process | Select-Object -First 10"
Recommendation

Review generated shell/PowerShell commands before execution, avoid passing untrusted text directly into commands, and keep actions as specific as possible.

What this means

The agent may be able to read or modify private Windows files that are accessible to the current user.

Why it was flagged

The skill documents access to Windows user files from WSL. This is purpose-aligned, but it means the agent acts with the user's local file permissions.

Skill content
cat /mnt/c/Users/Username/Desktop/file.txt; cp /mnt/c/Users/Username/Downloads/file.zip /mnt/c/Users/Username/Desktop/
Recommendation

Only request file operations on specific files or folders, and do not use this skill with prompts or content you do not trust.