← 返回 Skills 市场
133
总下载
0
收藏
0
当前安装
2
版本数
在 OpenClaw 中安装
/install wsl-windows-bridge
功能描述
WSL ↔ 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...
安全使用建议
Do not run setup.sh or install this skill until you verify the missing wrapper scripts. Request the actual win-* wrapper scripts (win-python, win-ps, win-cmd, win-copy, win-run-py, win-path) and review their contents: they will be the components that invoke Windows executables and could execute arbitrary commands or move files. Confirm that the wrappers only do what you expect (path conversion, controlled command invocation) and do not phone home or exfiltrate data. If you proceed: run setup.sh manually in an interactive shell (so you can answer prompts), inspect the generated ~/.openclaw/env.windows.sh before sourcing it, and avoid running it with elevated privileges. Finally, consider the risk that enabling an LLM agent to use this bridge grants it the ability to run Windows processes and access Windows files — only enable autonomous invocation for trusted agents and after reviewing the wrapper code.
功能分析
Type: OpenClaw Skill
Name: wsl-windows-bridge
Version: 0.2.0
The skill bundle provides a bridge for WSL2 to execute commands on the Windows host system via PowerShell, CMD, and Python. While these capabilities are clearly aligned with the stated purpose of the tool, the ability to bypass WSL2 isolation and execute arbitrary commands on the host OS is an inherently high-risk capability. The setup script (setup.sh) and environment configuration (env.windows.sh) appear to be legitimate administrative tools without evidence of intentional malice or data exfiltration, but the broad access to the host environment warrants a cautious classification.
能力标签
能力评估
Purpose & Capability
The skill claims six wrapper commands (win-python, win-ps, win-cmd, win-copy, win-run-py, win-path) and documents them in SKILL.md/README, but the distributed package only contains two script files (setup.sh and env.windows.sh). The actual wrapper executables (win-*) are not present in the file listing. setup.sh attempts to copy scripts named win-* from the scripts directory; if those wrappers are absent the advertised functionality will not be installed. This is an inconsistency between claimed capabilities and included files.
Instruction Scope
Instructions are explicit and limited to installing wrappers into ~/.openclaw/bin, generating an env file, and verifying installed wrappers. The setup flow is interactive (read -p) and the README notes non-interactive exec considerations. The instructions will source env files and then invoke win-* wrappers; because wrappers are missing, verification may fail. The instructions also enable cross-system execution of Windows commands (PowerShell/CMD) and filesystem access — that behavior is coherent with the stated purpose but is powerful: any wrapper that executes user-supplied commands can run arbitrary Windows code and access Windows files. The wrappers themselves are not provided for review, which prevents a full scope assessment.
Install Mechanism
No external downloads or remote installs; installation is local copying into the user's home directory (~/.openclaw). setup.sh creates directories and writes an env file under the user's home. This is a low-risk install mechanism in terms of supply-chain downloads.
Credentials
The skill does not request credentials or unusual environment access. It defines environment variables for WIN_* paths (WIN_ROOT, WIN_PYTHON, WIN_PS, etc.) which are appropriate for a WSL↔Windows bridge. No unrelated secrets or external service keys are requested.
Persistence & Privilege
The skill does not request 'always' inclusion and does not modify system-wide settings beyond writing files under the installing user's ~/.openclaw/ directory. However, because the functionality bridges into Windows and allows executing Windows commands, granting the skill autonomous invocation (the platform default) would increase risk: an autonomous agent could execute Windows processes and read/write Windows files. This is a contextual caution, not a direct misconfiguration in the package.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install wsl-windows-bridge - 安装完成后，直接呼叫该 Skill 的名称或使用
/wsl-windows-bridge触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v0.2.0
- Added or modified environment setup scripts: env.windows.sh and setup.sh.
- Improved automatic configuration and environment variable handling for cross-system integration.
- Enhanced setup process for easier installation and compatibility with different Windows Python paths.
v0.1.0
wsl-windows-bridge 0.1.0 – Initial public release
- Provides cross-system wrappers (win-python, win-ps, win-cmd, win-copy, win-run-py, win-path) for WSL2 ↔ Windows interoperability.
- Enables WSL2 users to invoke Windows Python (Anaconda or any), run PowerShell/CMD scripts, access and modify files, and convert paths across systems.
- Includes auto-detect setup script and environment configuration for seamless integration.
- Suitable for quantitative trading workflows (QMT/xtquant), automation, and cross-platform scripting.
- MIT licensed, with support for WSL2 (Ubuntu), Windows 10/11, and Windows Python.
元数据
常见问题
WSL Windows Bridge 是什么？
WSL ↔ 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... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 133 次。
如何安装 WSL Windows Bridge？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install wsl-windows-bridge」即可一键安装，无需额外配置。
WSL Windows Bridge 是免费的吗？
是的，WSL Windows Bridge 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
WSL Windows Bridge 支持哪些平台？
WSL Windows Bridge 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 WSL Windows Bridge？
由 DEACONHAN（@deaconhan）开发并维护，当前版本 v0.2.0。
推荐 Skills