Capture Windows Screen

Capture the current Windows desktop from this WSL/OpenClaw environment and return the PNG path for inspection or delivery. Use when the user asks to screensh...

Security Scan

The skill's files and instructions match its stated purpose (taking a Windows screenshot from WSL and staging the PNG); nothing requested is out of proportion, though it relies on a Windows helper script you must trust and uses a few hard-coded paths.

Purpose & Capability

The skill's name/description match what it does: the included shell script invokes PowerShell to run a Windows-side helper and copies the produced PNG into a staging directory. The Windows helper path (C:\OpenClaw\capture-screen.ps1), the mirrored path (/mnt/c/OpenClaw/latest-screen.png), and a user-specific workspace (/home/lhs/...) are assumed rather than declared; this is coherent for the stated task but brittle and user-specific.

Instruction Scope

SKILL.md and the script stay within screenshot capture and staging. The script runs PowerShell with -ExecutionPolicy Bypass to execute the external helper script — expected for invoking a Windows helper but means the Windows-side script can run arbitrary PowerShell. The instructions do not read unrelated environment variables or exfiltrate data to external endpoints.

Install Mechanism

No install step or external downloads. This is an instruction-only skill with a small packaged shell script — low install risk.

Credentials

The skill requests no credentials or env vars by metadata, and the script lets users override WIN_PS, OUT_WSL, and STAGE_DIR. However it assumes access to the Windows filesystem via /mnt/c and uses hard-coded paths (C:\OpenClaw, /home/lhs). These are reasonable for capturing a desktop image but require that the helper script and those paths exist and are trusted.

Persistence & Privilege

always is false and the skill is user-invocable. It does not modify other skills or system-wide settings and does not request permanent presence or elevated platform privileges.

Assessment

This skill appears to do what it says: call a Windows PowerShell helper to create a PNG and copy it into a staging folder. Before installing/using it, verify that C:\OpenClaw\capture-screen.ps1 exists and is trusted (it will be run under PowerShell with -ExecutionPolicy Bypass and could execute any PowerShell commands). Also confirm the hard-coded paths (/home/lhs/.openclaw/... and /mnt/c/OpenClaw/...) match your environment or override them by setting WIN_PS, OUT_WSL, or STAGE_DIR. If you cannot inspect the Windows helper or do not trust the machine environment, do not run the skill.

Use the bundled script for screenshot requests in this environment. It calls the Windows PowerShell helper, copies the PNG into a chosen staging folder, and prints the staged path.

Use two staging modes:

• Analysis / inspection: keep the default workspace tmp-media/ staging.
• Messaging-surface delivery: prefer ~/.openclaw/media/outbound/ so the file is already in OpenClaw's managed outbound media store.

Quick workflow

1. For analysis or inspection, run bash scripts/capture-windows-screen.sh from this skill directory.
2. For delivery back to a chat app, run STAGE_DIR=/home/lhs/.openclaw/media/outbound bash scripts/capture-windows-screen.sh.
3. Treat the printed path as the staged screenshot to use next.
4. If the user wants the image in chat, prefer the managed outbound path from step 2 and send it with a bare MEDIA: line when possible.
5. If the user wants analysis, inspect the staged image after capture.

Commands

Analysis / inspection path:

bash scripts/capture-windows-screen.sh

Delivery-safe path for chat apps:

STAGE_DIR=/home/lhs/.openclaw/media/outbound bash scripts/capture-windows-screen.sh

Expected output:

/home/lhs/.openclaw/workspace/tmp-media/latest-screen-YYYYMMDD-HHMMSS.png

or, for delivery-safe staging:

/home/lhs/.openclaw/media/outbound/latest-screen-YYYYMMDD-HHMMSS.png

Environment assumptions

This skill assumes these host-side paths exist:

• PowerShell: /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe
• Capture helper: C:\OpenClaw\capture-screen.ps1
• Screenshot output: C:\OpenClaw\latest-screen.png
• WSL mirror path: /mnt/c/OpenClaw/latest-screen.png
• Workspace staging directory for inspection copies: /home/lhs/.openclaw/workspace/tmp-media
• Managed outbound media store for delivery retries / chat attachments: /home/lhs/.openclaw/media/outbound

Failure handling

• If PowerShell or the helper script is missing, check local machine-specific notes before changing paths.
• If the command succeeds but the PNG is missing, rerun once, then verify the helper still writes to C:\OpenClaw\latest-screen.png.
• If the browser shows the image but Telegram or another chat app does not receive it, assume the file stayed at local-preview level. Restage it into /home/lhs/.openclaw/media/outbound and retry using only the managed outbound path.
• Do not assume a workspace tmp-media/ path is delivery-safe just because the web UI can preview it.
• Do not invent alternate screenshot commands unless the configured path is clearly broken.