What problem does it solve? Setting up remote access to an OpenCode WebUI running inside WSL2 requires manual systemd unit authoring, credential wiring, and Tailscale reverse-proxy configuration. This Skill automates that entire setup so a phone or remote browser on the same tailnet can reach the WebUI over HTTPS. ## Core Features & Use Cases - Systemd user service hosting: Generates or updates a systemd user unit (atomic write), cleans up legacy opencode web processes, starts the service, and waits for active state plus port readiness. - Tailscale serve configuration: Configures the Windows host's tailscale serve to proxy HTTPS traffic to localhost:PORT, then parses and reports the tailnet URL. - Status and partial modes: Supports --status-only checks and --restart-serve-only reconfiguration without restarting the WSL service. - Use Case: You are working in a cross-device emit/apply workflow and need a teammate's phone to open your OpenCode WebUI. Run the Skill to bring up the service, configure Tailscale, and receive the shareable HTTPS URL with the auth username. ## Quick Start Ask the assistant to start the OpenCode server so the WebUI is reachable from your phone over Tailscale.