OpenClaw Tailscale Remote Access

Configure or repair OpenClaw remote access over Tailscale with a directly executable workflow: inspect state, apply the gateway config, enable Tailscale Serv...

This skill appears to do what it advertises: it will read and overwrite your OpenClaw config (~/.openclaw/openclaw.json, with a timestamped backup), restart the openclaw-gateway user service, and run tailscale commands (serve, up, reset). Before using it: 1) verify you are on a safe management session (not a Tailscale SSH session) as the skill warns; 2) confirm the exact path to your openclaw.json and any gateway token you intend to insert; 3) inspect the bundled scripts (they are small and human-readable) and test them in a non-production environment if possible; 4) note the metadata omission (the registry did not declare the config path) and ensure the skill will operate on the correct config file. If you are uncomfortable with automatic config changes, run the inspect script first and run apply_gateway_config.py manually after reviewing the backup it will create.

Type: OpenClaw Skill Name: openclaw-tailscale-remote-access Version: 1.0.1 The skill bundle provides a workflow for configuring remote access via Tailscale Serve, which involves high-risk capabilities such as modifying system configuration files, managing systemd services, and executing network commands. While the scripts (e.g., `apply_gateway_config.py` and `configure_tailscale_serve.sh`) are well-documented and include safety checks to prevent connection loss, they handle sensitive gateway tokens in plaintext via command-line arguments and stdout. Under the provided criteria, the use of shell, network, and file access for remote access configuration—even when aligned with the stated purpose—is classified as suspicious.