Windows Remote

Control remote Windows machines via SSH. Use when executing commands on Windows, checking GPU status (nvidia-smi), running scripts, or managing remote Windows systems. Triggers on "run on Windows", "execute on remote", "check GPU", "nvidia-smi", "远程执行", "Windows 命令".

Security Scan

The skill's files, instructions, and required environment variables are consistent with a remote-Windows-via-SSH utility and do not request unrelated credentials or install arbitrary code.

Purpose & Capability

Name/description (remote Windows control via SSH) align with required binaries (ssh) and required env vars (WINDOWS_SSH_HOST, WINDOWS_SSH_USER). The included scripts (ssh/scp wrappers) directly implement the stated functionality.

Instruction Scope

SKILL.md only instructs setting SSH-related env vars and running the provided scripts to exec, upload, download, and query GPU status. The scripts accept arbitrary commands to run on the configured host (expected for a remote-control skill). Note: the scripts set StrictHostKeyChecking=no which weakens SSH host-key verification (security tradeoff, not incoherent).

Install Mechanism

This is instruction-only with no install spec — nothing is downloaded or written by an installer. The only runtime dependency is the ssh binary, which is reasonable for the described purpose.

Credentials

Required env vars (host, user) and optional SSH-related vars (port, key, timeout) are appropriate and proportional to a remote-SSH skill. No unrelated secrets or external service credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges or modify other skills. It suggests storing its own env in the user's ~/.openclaw/openclaw.json (expected configuration guidance). Model/autonomous invocation is enabled by default (normal for skills) but not combined with other concerning privileges.

Assessment

This skill appears to do exactly what it claims: run SSH/SCP commands against a configured Windows host. Before installing, ensure you: (1) only point WINDOWS_SSH_HOST and WINDOWS_SSH_USER at machines you trust, (2) protect your SSH private key (use key files with tight permissions), (3) be aware the scripts disable host-key checking (StrictHostKeyChecking=no) which makes MITM attacks easier — consider enabling host-key checking if you can, and (4) remember the skill can run arbitrary commands on the configured host, so do not expose it to untrusted networks or machines.

Windows Remote Control

Execute commands on remote Windows machines via SSH.

Configuration

Set environment variables in ~/.openclaw/openclaw.json under skills.windows-remote.env:

{
  "skills": {
    "windows-remote": {
      "env": {
        "WINDOWS_SSH_HOST": "192.168.1.100",
        "WINDOWS_SSH_PORT": "22",
        "WINDOWS_SSH_USER": "Administrator"
      }
    }
  }
}

Or export directly:

export WINDOWS_SSH_HOST="192.168.1.100"
export WINDOWS_SSH_PORT="22"
export WINDOWS_SSH_USER="Administrator"

Quick Commands

Check Connection

scripts/win-exec.sh "echo connected"

GPU Status

scripts/win-exec.sh "nvidia-smi"

Run PowerShell

scripts/win-exec.sh "powershell -Command 'Get-Process | Select-Object -First 10'"

Execute Script

scripts/win-exec.sh "python C:\\path\\to\\script.py"

Script Reference

win-exec.sh

Execute a single command on the remote Windows machine.

scripts/win-exec.sh "<command>"

win-gpu.sh

Quick GPU status check (nvidia-smi wrapper).

scripts/win-gpu.sh
scripts/win-gpu.sh --query  # Compact output

win-upload.sh

Upload files to the remote machine via SCP.

scripts/win-upload.sh <local-file> <remote-path>

win-download.sh

Download files from the remote machine.

scripts/win-download.sh <remote-path> <local-file>

Common Tasks

Check if Ollama is Running

scripts/win-exec.sh "tasklist | findstr ollama"

Start a Service

scripts/win-exec.sh "net start <service-name>"

Run Python with GPU

scripts/win-exec.sh "python -c \"import torch; print(torch.cuda.is_available())\""

Check Disk Space

scripts/win-exec.sh "wmic logicaldisk get size,freespace,caption"

Troubleshooting

Issue	Solution
Connection refused	Check SSH service: Get-Service sshd
Permission denied	Verify SSH key in ~/.ssh/authorized_keys or administrators_authorized_keys
Timeout	Check firewall rules, verify IP/port
Command not found	Use full path or check PATH on Windows

Security Notes

• Use SSH keys instead of passwords
• Keep private keys secure (chmod 600)
• Consider using Tailscale for cross-network access