Skills/ClawHub/pc-control

pc-control@1.0.0

VERIFIED· install only

Publisher claims: "Remote Windows desktop control from WSL/Linux via screenshot + mouse/keyboard simulation. Use when: user asks to control their PC, click something, open an a..." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher zeron-g · publishing for 268 daysInstalls 1,776Last detonated 1 h ago
$clawhub install pc-control
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 3 of 3 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-21 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.1sprocessexec /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe
0.1sprocessexited 1: FileNotFoundError: [Errno 2] No such file or directory: '/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessbundled script run in the sandbox with no arguments
0.4snetworkGET http://127.0.0.1:18888/status · not in the allow-list, refused
0.4sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.5sprocessexited 1: ModuleNotFoundError: No module named 'mss'
0.5sprocess3 of 3 bundled scripts run with no arguments
0.5sprocessscript backend runs setup only
0.5sprocessscript backend runs setup only
0.5sprocesssecond launch, clock +45 days, CI unset
0.6sprocessexec /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe
0.6sprocessexited 1: FileNotFoundError: [Errno 2] No such file or directory: '/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'

Static findings

MEDIUM
Python subprocess execution detectedscripts/launcher.py:35 · Python subprocess execution detectedresult = subprocess.run(["wslpath", "-w", wsl_server], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/launcher.py:71 · Python subprocess execution detectedsubprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/install.py:16 · Python subprocess execution detectedresult = subprocess.run([POWERSHELL, "-Command", cmd], capture_output=True, text=True, timeout=120)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/launcher.py:43 · Python subprocess execution detectedsubprocess.run([POWERSHELL, "-Command", cmd], capture_output=True, timeout=15)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈700 tok
1 file · 8 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.