WSL Windows Bridge
v0.1.0WSL ↔ Windows cross-system bridge for OpenClaw agents. Provides win-python / win-ps / win-cmd / win-copy / win-run-py / win-path to invoke Windows Python (An...
⭐ 0· 20·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
The skill provides wrappers to call Windows Python, PowerShell, CMD and path conversion from WSL. Declared required binaries (bash, wslpath, powershell.exe, cmd.exe) match that purpose and no unrelated credentials or services are requested.
Instruction Scope
SKILL.md instructs the user to run the included setup.sh which generates ~/.openclaw/bin/* wrappers and an env file to export WIN_* variables. That scope is consistent with the bridge purpose, but the setup script will write/overwrite files in the user's ~/.openclaw/bin and create ~/.openclaw/env.windows.sh without prompting for backups. The wrappers' contents were not provided for review here — those should be inspected because they will be executed with user privileges and may call PowerShell/CMD.
Install Mechanism
No remote downloads; the install is local (setup.sh copies and templates files into the user's home). This is lower risk than fetching arbitrary remote code, but it does write executables into ~/.openclaw/bin and generates an env file (persisting behavior). The script also uses sed replacement of a hardcoded /home/traceback placeholder when copying wrappers.
Credentials
The skill declares no required environment variables or credentials. The env file it generates exports WIN_* paths and prepends ~/.openclaw/bin to PATH — appropriate for the stated functionality. No unrelated secrets or external service tokens are requested.
Persistence & Privilege
always:false (normal). The skill persists by installing wrapper binaries and an env file into the user's home directory and requires sourcing that env to put wrappers on PATH. This is expected, but be aware the installed files will persist and can be invoked autonomously by the agent under normal platform behavior.
Assessment
This skill appears to do what it says: provide WSL→Windows command wrappers. Before installing, review the actual wrapper scripts (scripts/win-*) to ensure they don't execute unexpected remote commands or unescaped inputs. Back up any existing ~/.openclaw/bin files because setup.sh will copy/overwrite files without prompting. Note the template env.windows.sh contains a hardcoded /home/traceback path that setup.sh replaces when installing — don't source the template directly; use the generated ~/.openclaw/env.windows.sh. Run setup.sh interactively (it may prompt) and consider testing in a non-production environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk972ezxn09qtmyqxsqvpzp3m1h847wz0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🪟 Clawdis
Binsbash, wslpath, powershell.exe, cmd.exe