← ClaudeAtlas

wake-panellisted

Use when setting up remote wake-on-LAN, remote power control, or a machine-status dashboard reachable over Tailscale — including "wake my PC from my phone", "remote reboot my workstation", "WoL over VPN/WAN doesn't work", "GPU temp dashboard", or hosting a control panel on a NAS, Raspberry Pi, or other always-on device.
REMvisual/claude-wol-remote-access · ★ 1 · AI & Automation · score 69
Install: claude install-skill REMvisual/claude-wol-remote-access
# Wake Panel Build a password-protected web panel, hosted on an always-on device, that wakes and monitors the user's computers from anywhere on their tailnet. ## The one fact that drives the whole design **A Wake-on-LAN magic packet is a layer-2 broadcast. Tailscale is layer 3 and forwards no broadcast traffic.** A phone off the home LAN therefore cannot wake anything directly — not with Moonlight's "Wake PC", not with any WoL app, not through a Tailscale subnet router. This is not a limitation to engineer around; it is how WoL works. So the packet must originate on the LAN. An always-on device hosts a relay: ``` phone (anywhere) --Tailscale--> relay host --LAN broadcast--> target PC ``` The relay must NOT live on one of the machines being controlled — a PC cannot wake itself, and two PCs that are both off cannot wake each other. ## Running this Work through the stages in order. **Each stage ends with a gate — do not proceed past a failed gate.** Later stages assume earlier ones actually worked, and a silent failure at stage 3 surfaces as an inexplicable one at stage 6. Do as much as possible yourself over SSH. Hand the user a command ONLY when it needs local elevation, physical access, or a password you must not see. Read `reference/TROUBLESHOOTING.md` when anything fails. Nearly every failure in this domain has a specific, non-obvious cause already catalogued there. ### Stage 0 — Preflight Establish and confirm with the user: | Need | Why | |---|---| | An alway