← Back to Skills Marketplace
owlock

Windows Native Dialog

by Owlock · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ⚠ suspicious
172
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install windows-native-dialog
Description
Handles native Windows file picker dialogs from WSL2 using exec and PowerShell
Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill Name: windows-native-dialog Version: 1.0.2 The skill bundle instructs the OpenClaw agent to execute PowerShell commands on the Windows host from a WSL2 environment using the 'exec' tool. While the stated purpose is to handle native file picker dialogs, the use of shell execution targeting the host OS with placeholder paths (e.g., 'C:\path\to\script.py' in SKILL.md) and the request for broad tool permissions (tools.allow) represent a high-risk execution pattern. No clear evidence of malicious intent was found, but the approach bypasses standard security boundaries between the container/WSL and the host.
Capability Assessment
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.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install windows-native-dialog
  3. After installation, invoke the skill by name or use /windows-native-dialog
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Added skills comparison table for Windows desktop automation
v1.0.1
Added complete subir_video.py script and detailed prompt template
v1.0.0
Initial release of windows-native-dialog. - Enables handling of native Windows file picker dialogs from WSL2. - Uses exec and PowerShell to automate invisible dialog interactions. - Designed for workflows needing file uploads in browser automation scenarios. - Tested successfully with Meta Business Suite on Windows 10 + WSL2.
Metadata
Slug windows-native-dialog
Version 1.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Windows Native Dialog?

Handles native Windows file picker dialogs from WSL2 using exec and PowerShell. It is an AI Agent Skill for Claude Code / OpenClaw, with 172 downloads so far.

How do I install Windows Native Dialog?

Run "/install windows-native-dialog" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Windows Native Dialog free?

Yes, Windows Native Dialog is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Windows Native Dialog support?

Windows Native Dialog is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Windows Native Dialog?

It is built and maintained by Owlock (@owlock); the current version is v1.0.2.

💬 Comments