vscode-tunnel

Start VS Code Remote Tunnel in Docker containers for remote terminal access

This skill appears to do what it claims: it downloads the VS Code CLI from Microsoft's servers into ~/.vscode-cli and runs it to create a remote tunnel. Before installing, consider: 1) the script will execute a downloaded binary — only use it if you trust the source or prefer to preinstall/verify the CLI yourself; 2) creating a VS Code remote tunnel grants remote access to the container once you authorize via your Microsoft account — ensure you want that exposure and run it in a controlled environment; 3) logs and PID files are stored under the CLI_DIR (default ~/.vscode-cli) and may contain messages related to authorization — inspect them if you're concerned about sensitive data; 4) the script uses pgrep to find 'code tunnel' processes which may occasionally match unrelated processes, so status/stop behavior can be imperfect. If you want stronger assurance, review the downloaded CLI binary/checksums manually or run the skill in an isolated container.

Type: OpenClaw Skill Name: vscode-tunnel Version: 1.0.0 The skill downloads and executes a binary from a remote URL (code.visualstudio.com) using `curl` and `tar` in `tunnel.sh`. While the source is legitimate and the stated purpose (VS Code Remote Tunnel) is benign, the act of fetching and executing remote code is a high-privilege operation and introduces a supply chain risk. If the download source were compromised, this skill could be leveraged to execute arbitrary malicious code. The script correctly quotes user-provided arguments, preventing direct shell injection, and there are no signs of prompt injection against the agent in `SKILL.md` or other malicious behaviors like data exfiltration or unauthorized persistence mechanisms beyond the intended background tunnel process.