Windows-Android_SSH_Remote_Control

v1.0.0

Setup and guide for full remote control of a Windows PC from an Android device over the internet via SSH tunneling. Use for: remote desktop access, secure RD...

0· 97·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for jarbcs1-prog/windows-android-ssh-remote-control.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Windows-Android_SSH_Remote_Control" (jarbcs1-prog/windows-android-ssh-remote-control) from ClawHub.
Skill page: https://clawhub.ai/jarbcs1-prog/windows-android-ssh-remote-control
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install windows-android-ssh-remote-control

ClawHub CLI

Package manager switcher

npx clawhub@latest install windows-android-ssh-remote-control
Security Scan
Capability signals
CryptoRequires wallet
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Windows <-> Android remote control via SSH) matches the included docs and example script. The steps (enable RDP, install OpenSSH server, configure port forwarding or use Tailscale, create SSH tunnel in ConnectBot, point RDP client to localhost) are exactly what someone building this capability would need. No unrelated credentials, binaries, or services are requested.
Instruction Scope
The SKILL.md and reference docs provide specific PowerShell commands and step‑by‑step manual setup instructions; they do not instruct the agent to read unrelated system files or exfiltrate data. Note: files reference an absolute path (/home/ubuntu/skills/...) which is simply where the skill's docs live in the package and may not match a user's environment. The instructions do recommend actions that require administrator privileges (installing OpenSSH, changing firewall/router settings) and shipping RDP over the internet is explicitly warned as risky — the skill itself advises using SSH keys or a VPN (Tailscale) to mitigate risk.
Install Mechanism
There is no install spec — this is instruction-only with a small placeholder example.py. Nothing is downloaded or written to disk by an installer step, so there is no high-risk install mechanism in the package.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That aligns with its purpose as a documentation/guide skill. The included example script is a harmless placeholder and does not access secrets or external endpoints.
Persistence & Privilege
The skill does not request persistent or elevated platform privileges (always:false). It does not attempt to modify other skills or system-wide agent settings. Runtime instructions require local administrative actions on the user's Windows machine, which is appropriate for the task.
Assessment
This skill is a documentation/guide package and appears internally consistent, but it instructs you to perform privileged actions on your Windows PC (install OpenSSH, change firewall/router settings, enable RDP). Before following its steps: (1) prefer a private mesh VPN like Tailscale/ZeroTier instead of exposing SSH or RDP to the public Internet; (2) use SSH key authentication and disable password auth; (3) avoid forwarding port 22 to the Internet unless you understand the risk and have strong protections (keys, nonstandard port, fail2ban, etc.); (4) verify you are comfortable granting Administrator rights to make the Windows changes; (5) be aware the package contains only documentation and a placeholder script — no hidden endpoints were found, but also no author or homepage is provided, so if you need automated tooling or installers, prefer well‑maintained sources or official vendors. If you want greater assurance, ask the publisher for a maintainer identity, official docs, or a reputation/source (GitHub repo, homepage) before proceeding.

Like a lobster shell, security has layers — review code before you run it.

latestvk97asgrmt1dx7qv04484tapp4n84ns8b
97downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Windows-Android SSH Remote Control

This skill provides a secure workflow for setting up and using full remote control of a Windows PC from an Android device using SSH tunneling. This method is more secure than exposing RDP directly to the internet.

Prerequisites

  • Windows PC: Windows 10/11 Pro or Enterprise (Home edition does not support RDP server).
  • Android Device: With internet access.
  • Apps: ConnectBot (or Termux) and Microsoft Remote Desktop on Android.

Workflow Overview

  1. Windows Setup: Enable RDP and OpenSSH Server.
  2. Network Configuration: Port forward SSH (Port 22) or use a VPN/Tailscale.
  3. Android Setup: Configure an SSH tunnel in ConnectBot.
  4. Remote Connection: Connect via Microsoft Remote Desktop to localhost.

Detailed Instructions

1. Windows PC Configuration

Read the detailed Windows setup guide for enabling RDP and OpenSSH:

  • /home/ubuntu/skills/windows-android-ssh-remote/references/windows_setup.md

2. Android Device Configuration

Read the detailed Android setup guide for configuring the SSH tunnel and RDP client:

  • /home/ubuntu/skills/windows-android-ssh-remote/references/android_setup.md

Security Best Practices

  • Use SSH Keys: Disable password authentication in sshd_config and use public/private key pairs for maximum security.
  • Change Default Port: Consider changing the SSH port from 22 to a non-standard port (e.g., 2222) to reduce automated bot attacks.
  • Use a VPN: For the highest security, use a mesh VPN like Tailscale or ZeroTier instead of port forwarding. This eliminates the need to expose any ports to the public internet.

Troubleshooting

  • Connection Refused: Ensure the sshd service is running on Windows and the firewall allows Port 22.
  • RDP Fails: Verify that the SSH tunnel is active in ConnectBot and that you are connecting to 127.0.0.1 in the RDP app.
  • NLA Error: If you get a Network Level Authentication error, ensure your Windows user account has a password and is part of the "Remote Desktop Users" group.

Comments

Loading comments...