一键导入
hue-lights
Control Philips Hue smart lights. Use when asked about lights, lighting, brightness, room lighting, or turning lights on/off.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Control Philips Hue smart lights. Use when asked about lights, lighting, brightness, room lighting, or turning lights on/off.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | hue-lights |
| description | Control Philips Hue smart lights. Use when asked about lights, lighting, brightness, room lighting, or turning lights on/off. |
| allowed-tools | Bash(hue:*) |
| metadata | {"openclaw":{"emoji":"L","requires":{"bins":["hue"]}}} |
Control Philips Hue lights via the hue CLI. Two bridges (Crosstown and Cabin) with credentials managed via 1Password. The CLI auto-detects local vs remote access — works from any device on the tailnet.
hue status
hue on <room>
hue on <room> 50 # on at 50% brightness
hue off <room>
hue bri <room> 75
hue color <room> warm # warm white
hue color <room> cool # cool white
hue color <room> daylight # daylight
hue color <room> red # named colors: red, orange, yellow, green, blue, purple, pink
hue scene <room> <scene-name>
hue all-on
hue all-off
hue lights
Room names are fuzzy-matched — use any substring (e.g. "bed" for Bedroom, "living" for Living room).
There are two homes with overlapping room names. You must always select the correct bridge.
| Home | Location | Flag | Unique rooms |
|---|---|---|---|
| Crosstown | Boston (Crosstown residence) | --crosstown (default) | Entryway, Movie Room, Cat Room, Downstairs, Master Bath |
| Cabin | Philly | --cabin | Bathroom, Hallway, Solarium, Staircase |
Shared room names (exist in both homes): Kitchen, Living room, Bedroom, Office
When the user mentions a shared room name, determine the correct home from context:
hue --cabin on kitchenhue on kitchen (or hue --crosstown on kitchen)When running routines or multi-room commands, make sure every command targets the same bridge.
The CLI tries the local bridge first (LAN), then falls back to the Hue Cloud API (remote). Override with HUE_MODE=local or HUE_MODE=remote.
Both bridges have remote API access. Use --crosstown (default) or --cabin to select, or HUE_BRIDGE=cabin.
hue --cabin status # Cabin (Philly) lights
hue --crosstown on kitchen # Crosstown (Boston) kitchen
hue status # defaults to Crosstown
1Password items:
hue CLI at /opt/homebrew/bin/hue — it is already paired, configured, and has credentials for both bridges. Do NOT use openhue, do NOT install any other Hue CLI (brew install anything), do NOT use raw Hue REST API curl calls, and do NOT attempt bridge pairing or setup. Everything is already working. Just run hue commands.hue status first to show the user current state before making changeshue color bedroom warm then hue bri bedroom 30)Read upcoming OpenTable reservations or handle attended ad-hoc OpenTable availability and exact-approval booking. Use for OpenTable account reads, attended restaurant searches, or a user-confirmed one-off reservation; route canonical recurring date-night, double-date, and quarterly-group jobs to the restaurant-book skill instead.
Stage tightly scoped background reservation monitoring for OpenTable or Resy after explicit bounded preauthorization. Resy may auto-book after approval; OpenTable remains notification-only until this runtime adapter integrates the deployed live reservations reader. Not for one-shot search, attended booking, or cancellation.
Search Resy, inspect availability, and handle attended ad-hoc Resy booking. Route canonical recurring date-night, double-date, and quarterly-dinner jobs to restaurant-book, and use restaurant-snipe only for bounded cancellation monitoring. Never use this skill for unattended cancellation.
Safely plan or execute a canonical standing-authorized restaurant cron scope across both Resy and OpenTable. Use only for the tracked date-night, double-date, and quarterly-dinner jobs; use the provider skills for attended ad-hoc work and restaurant-snipe for bounded monitoring.
Safely use exact 1Password fields during attended interactive work and maintain the protected OpenClaw secrets cache. Use for passwords, API keys, credentials, payment data, cache refreshes, or diagnosing credential access. Never use `op` from a LaunchAgent or any child process it starts.
Diagnose and fix 1Password CLI hangs or repeated TCC prompts in macOS LaunchAgent and other unattended contexts by converting the complete process tree to a protected cache-only credential contract.