Windows Native Dialog

Handles native Windows file picker dialogs from WSL2 using exec and PowerShell

Security Scan

The skill's behavior (running arbitrary Windows PowerShell/python commands from WSL2 and asking for broad runtime/fs tool permissions) is coherent with its stated purpose but the instructions omit important declarations and enable execution of arbitrary local code, which is risky and unexplained.

Purpose & Capability

The name/description (handle native Windows file pickers from WSL2 via exec+PowerShell) matches the instructions: it uses /mnt/c/.../powershell.exe to run a Windows-side python script. However, the skill metadata declares no required binaries while the runtime instructions clearly rely on powershell.exe and a Windows Python interpreter/script — these should have been declared.

Instruction Scope

Runtime instructions explicitly tell the agent to execute a Windows PowerShell command that runs a local python script (C:\path\to\script.py). That requires reading/executing arbitrary files on the host and gives the agent the ability to run any code on the Windows side. The SKILL.md also instructs setting tools.allow to include group:fs and group:runtime, broad permissions that enable file access and arbitrary command execution. The instructions do not specify where script.py comes from or require the user to vet its contents.

Install Mechanism

There is no install spec and no files beyond SKILL.md, so nothing is written to disk by the skill itself. This lowers installation risk.

Credentials

The skill requests (in SKILL.md) enabling broad tool groups (browser, runtime, fs, web) to work, but the registry metadata lists no required env vars or binaries. Asking for filesystem and runtime execution rights is proportionate to the stated goal, but it is a sensitive capability and should be clearly declared and justified in the metadata and documentation.

Persistence & Privilege

The skill is not always-enabled and does not request persistent presence or modify other skills' configs. Agent autonomous invocation is allowed (platform default) but not by itself a problem.

What to consider before installing

This skill will ask the agent to run Windows-side PowerShell commands from WSL2 that execute a local Python script. That gives the agent the ability to run arbitrary code on your Windows host and access files. Before installing or using it: (1) verify and inspect any script referenced (C:\path\to\script.py) — do not run unknown scripts; (2) prefer the skill declare required binaries (powershell.exe, python) and the exact commands it will run; (3) only enable the requested tool groups (fs/runtime) for this skill if you trust it and have reviewed the scripts; (4) consider running this workflow in an isolated/test environment rather than a primary machine. The metadata omission (no required binaries listed) and the broad runtime/fs permissions are why this skill is suspicious rather than clearly benign.

Teaches OpenClaw how to handle native Windows file picker dialogs invisible to browser-automation.

Requirements

openclaw config set tools.allow '["browser","group:runtime","group:fs","group:web"]'

Prompt

STEP 1 - browser-automation: click upload button. STEP 2 - exec: /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe -Command "python C:\path\to\script.py video.mp4" STEP 3 - browser-automation: click Publish.

Tested

Meta Business Suite on Windows 10 + WSL2. Result: success. Related: Issue #52525, PR #39407 — author @owlock

Skills comparison — desktop automation for Windows + WSL2

Skill	Autonomy	OS	Best for
clawd-cursor	95%	Win/Mac/Linux	Full desktop — sees screen + acts
matagul/desktop-control	75%	Windows native	Mouse + keyboard via pyautogui
desktop-computer-automation	70%	Win/Mac	Desktop screenshot + native windows
pc-control	65%	Win + WSL2	FastAPI bridge WSL2 ↔ Windows
browser-automation	60%	All	Browser-only via CDP
owlock/windows-native-dialog	55%	Win + WSL2	exec+PowerShell workaround

Note: matagul/desktop-control requires OpenClaw native on Windows. clawd-cursor is the most autonomous option for Windows users.