WoL Wakeup

局域网唤醒 (WoL) 自动化技能。支持工作流模式和单行命令模式，多轮对话添加设备，无需大模型。使用方式：1) "帮我开机"→列表 2) "开机 - 设备名"→唤醒 3) "添加网络唤醒"→工作流 4) "列表"→查看 5) "删除 - 设备名"→删除

Before installing, review and harden the deployment: 1) Search the repo/docs for any hard-coded token (examples in INTEGRATION_GUIDE/REPORT) and replace with a generated secret; never use published example tokens in production. 2) Ensure you set a strong HOOK_TOKEN (or --token) and verify openclaw_hook.py starts with that token; do not leave token unset (the server currently accepts requests when no token is configured). 3) Confirm which OpenClaw config file the installer will modify (install.py writes ~/.openclaw/config.json while docs reference openclaw.json); back up your existing OpenClaw config before running update scripts. 4) Inspect the systemd service file and decide whether to enable a user/system service; run install steps manually if you prefer (the install script will attempt to enable/start systemd). 5) Protect log and token files (HOOK_LOG_FILE, .hook_token, ~/.openclaw/*) with restrictive file permissions and consider rotating tokens. 6) Because the hook logs inbound message content, consider whether PII may be written to hook.log and control access to that file. 7) If you want to test safely, run the hook in an isolated environment or container, verify behavior, then adopt in production only after addressing the above. If you want, I can point out exact files/lines to change to fix the token/config issues and secure logging.

Type: OpenClaw Skill Name: wol-wakeup Version: 1.0.0 The wol-wakeup skill bundle provides a Wake-on-LAN (WoL) utility for OpenClaw, featuring a multi-turn workflow engine to simplify device management. It implements an 'Internal Hook' architecture where a local HTTP server (scripts/openclaw_hook.py) intercepts messages to handle stateful dialogues (e.g., adding a device step-by-step) without relying on LLM inference for every turn. The installation process (scripts/install.py and scripts/update_openclaw_config.py) modifies the OpenClaw configuration and sets up a systemd user service to ensure the hook server runs in the background. These high-privilege actions are clearly documented, aligned with the stated purpose of the skill, and lack any indicators of malicious intent such as data exfiltration or unauthorized remote access.