Wcs Helper Network Skill

SSH tunnel for China servers to access internationally blocked sites (GitHub, ClawHub, HuggingFace, arXiv, Google, YouTube). Password-auth based, one-command...

Security Scan

The skill's stated purpose (an SSH SOCKS5 tunnel) is plausible, but the package is internally inconsistent and asks you to submit plaintext SSH passwords via chat and to rely on missing shell scripts — these are red flags you should resolve before installing.

Purpose & Capability

The described capability (autossh + sshpass + proxychains to provide a SOCKS5 tunnel) is coherent with the skill's purpose. The _meta.json lists reasonable runtime requirements (autossh, proxychains4, sshpass). However the packaged files do not include the many referenced helper scripts (connect.sh, sg-*.sh, etc.) that the README and SKILL.md repeatedly instruct you to run; the Python handler calls a connect.sh path under the skill directory but that script is absent from the bundle. This missing-file mismatch is unexpected and unexplained.

Instruction Scope

SKILL.md explicitly instructs users to send server IP/port/username/password via a Feishu private chat slash command. That means sensitive SSH passwords are entered into a messaging channel and will be processed by the agent. The runtime code (tunnel_handler.py) delegates to a connect.sh script (not present) which would presumably create ~/.wcs_tunnel.conf and may install systemd services. The instructions therefore require handling and persistent storage of plaintext passwords and encourage use of sshpass (which places passwords on the command line), both of which expand scope beyond a simple helper and increase risk of credential exposure.

Install Mechanism

There is no install spec (instruction-only), and only one code file is packaged (scripts/tunnel_handler.py). README/SKILL.md describe many shell scripts and an install-service step that would create systemd units, but those scripts are not present in the manifest. Because the Python handler calls an external connect.sh that isn't included, the package as provided is incomplete — if the missing scripts are fetched later from an external source at install time, that would be a higher-risk install pattern (arbitrary code from network).

Credentials

The manifest itself does not request environment variables, but README suggests environment variables for automation (TUNNEL_HOST, TUNNEL_USER, TUNNEL_PASS) and SKILL.md/README state credentials are stored in ~/.wcs_tunnel.conf. The skill asks the user to provide high-sensitivity secrets (SSH password) via chat, and recommends sshpass (which exposes passwords to process listings). Requesting and storing a plaintext SSH password is disproportionate compared with the minimal claim 'start an SSH tunnel' — a more secure, proportional design would recommend an SSH key or prompt locally rather than sending passwords via chat.

Persistence & Privilege

The skill does not set always: true and does not itself modify other skills. However SKILL.md/README describe an 'install-service' option to create a systemd service for auto-starting the tunnel. If connect.sh implements that, it grants system-level persistence (systemd unit). Because connect.sh is not present, we cannot inspect what that action would do, so this is a cautionary note: a legitimate feature but one that requires elevated privileges and should be audited before being run.

What to consider before installing

This skill may be trying to do what it claims (create an SSH SOCKS5 tunnel), but there are several red flags you should address before installing: - Missing scripts: The package only includes tunnel_handler.py, but SKILL.md and README repeatedly refer to connect.sh and many helper scripts that are not present. Do not run commands that download or execute missing scripts from unknown URLs without inspecting them first. Ask the author for the full package or the missing files and inspect connect.sh and any systemd install scripts. - Password handling: The instructions tell you to send your server password in a chat command. That exposes the password to the messaging service, agent processing, and any logs. Prefer SSH key authentication and avoid sending secrets in chat. If you must use a password, verify where and how it is stored (inspect ~/.wcs_tunnel.conf) and ensure it is not sent to external endpoints. - sshpass risks: The skill recommends sshpass, which places the password on the command line and can be observed by other processes/users. Consider using key-based auth or an SSH agent instead. - systemd auto-start: The skill mentions installing a systemd service. Only allow that after reviewing the exact service file to confirm it does nothing unexpected. - If you still want to try it: run in an isolated VM/container, create a throwaway VPS account, replace password auth with a dedicated limited account, and audit the connect.sh and related scripts before giving any real credentials. If the author cannot provide the missing scripts for review, avoid installing.

WCS Helper: Network Tunnel

Access internationally blocked websites from your China-based server.

---

When You Need This

Scenario A — "git push keeps timing out"

git push github main
# → Connection timeout

→ /万重山-隧道-开启 → try push again → succeeds

Scenario B — "npm install keeps failing for a package from GitHub"

npm install some-github-package
# → network timeout

→ /万重山-隧道-开启 → npm works through tunnel

Scenario C — "HuggingFace model download is stuck"

huggingface-cli download ...
# → timeout or connection reset

→ /万重山-隧道-开启 → download completes through tunnel

Scenario D — "ClawHub skill install is super slow"

clawhub install author/skill
# → extremely slow, often fails

→ /万重山-隧道-开启 → ClawHub installs at full speed

---

Supported Sites

Site	Use Case	Status
GitHub	git clone/push, npm packages	✅
ClawHub	skill install, plugin browsing	✅
HuggingFace	model downloads, datasets	✅
arXiv	research paper access	✅
Google	search, fonts, analytics	✅
YouTube	video embeds, APIs	✅
Twitter/X	social media embeds	✅
Reddit	forum access, APIs	✅

---

Prerequisites

Required

• A server outside China (any VPS with SSH access)
  • Recommended: Tencent Cloud Singapore, AWS Singapore, or any international VPS
  • SSH password authentication must be enabled
• SSH password for that server
• Server's public IP address

Recommended

• autossh installed on your China server (auto-restarts tunnel if it drops)
  • Install: apt install autossh (Debian/Ubuntu)
• sshpass installed (for password-based SSH)
  • Install: apt install sshpass

Network Flow

Your China Server (autossh client)
        ↓ SSH tunnel (encrypted)
Singapore/International VPS (as SOCKS5 proxy)
        ↓
GitHub / ClawHub / HuggingFace / Google

---

Setup

1. Get a Tunnel Server

Any international VPS works. Recommended:

• Tencent Cloud Singapore (CNY ~15/month)
• AWS Singapore Free Tier
• DigitalOcean Singapore
• Vultr Tokyo/Singapore

Requirements:

• SSH password access enabled
• Port 22 (SSH) open to China IPs

2. Install the Skill

npx -y clawhub install guanqi0914/wcs-helper-network-skill

3. Configure with Your Server

Send this command via Feishu private chat:

/万重山-隧道-配置 服务器IP SSH端口 用户名 密码

Example:

/万重山-隧道-配置 43.134.164.43 22 ubuntu myPassword123

4. Start the Tunnel

/万重山-隧道-开启

You should see: ✅ Tunnel connected

5. Test It

curl --socks5 127.0.0.1:1080 https://api.github.com
# Should return: HTTP 200

---

All Commands

Command	What It Does
/万重山-隧道-配置 <IP> <端口> <用户> <密码>	Set up tunnel server credentials
/万重山-隧道-开启	Start the tunnel
/万重山-隧道-关闭	Stop the tunnel
/万重山-隧道-状态	Show tunnel connection status
/万重山-隧道-测试	Test tunnel speed
/万重山-隧道-帮助	Show help

---

Usage Tips

Before Running git/npm Commands

Send /万重山-隧道-状态 first. If you see "Tunnel: ✅", you're good. If "Tunnel: ❌", send /万重山-隧道-开启 first.

Tunnel Stays On Until You Close It

The tunnel runs in the background. Send /万重山-隧道-关闭 when you don't need international access any more.

Which Ports Are Proxied

Only TCP connections through the SOCKS5 proxy are tunneled:

• GitHub (443) ✅
• ClawHub (443) ✅
• HuggingFace (443) ✅
• Google (443) ✅

UDP traffic (some gaming, VoIP) is NOT proxied.

---

How It Works

Connection Process

1. autossh connects to your international server via SSH
   sshpass -p 'password' ssh -N -D 127.0.0.1:1080 user@server-ip

2. SSH creates encrypted tunnel

3. autossh monitors the tunnel every 30 seconds

4. If tunnel drops → autossh auto-restarts it

5. Applications use 127.0.0.1:1080 as SOCKS5 proxy

Without the Tunnel (Direct Connection)

China Server → GitHub/ClawHub/HuggingFace
  ↓
Connection timeout / reset / very slow

With the Tunnel

China Server → SSH Tunnel → International VPS → GitHub/ClawHub/HuggingFace
                         ↓
              Stable encrypted connection

---

Performance

Metric	Value
Tunnel latency	~50-100ms (China → Singapore)
GitHub clone speed	500KB/s - 5MB/s
ClawHub install	1-5 seconds
Proxy overhead	~5-10% bandwidth

---

Troubleshooting

"Tunnel: ❌ Connection failed" → Check server IP, SSH port, username, password → Make sure SSH password auth is enabled on your VPS

"Tunnel connects but git push still times out" → Try again — GitHub sometimes rate-limits tunnel IPs temporarily → If persistent, your VPS IP may be on GitHub's blacklist

"autossh process not running after server restart" → Send /万重山-隧道-开启 to restart manually → Or set up systemd service (advanced — see auto-fix.sh)

"SSH connection refused" → Check if port 22 is open on your VPS firewall → Try SSH port 2222 if 22 is blocked

---

Security Notes

• The tunnel only handles outbound connections from your China server
• Your VPS provider can see the traffic (GitHub, ClawHub, etc.) but NOT your China server's other traffic
• No data is stored on the VPS — only encrypted transit
• Tunnel credentials are stored locally in ~/.wcs_tunnel.conf (chmod 600)

---

Uninstall

# Stop tunnel
/万重山-隧道-关闭

# Remove skill files
rm -rf ~/.openclaw/workspace/skills/wcs-helper-network-skill
rm -f ~/.wcs_tunnel.conf