hue

# Philips Hue Use this skill for Philips Hue Bridge lighting inspection and guarded control. The primary path is local HTTPS to the Hue Bridge CLIP v2 API. Use the Hue Remote API only when the operator explicitly needs off-LAN control or local bridge access is unavailable. ## Safety Rules 1. Use `skills/hue/hue.cjs` for every supported Hue request shape. Do not handcraft CLIP v2 URLs or JSON bodies when the helper supports the action. 2. Read current light, room, zone, and scene state before changing lights. 3. Treat local reads as green, local light/group/scene/behavior changes as amber, off-LAN Remote API calls as amber, and bridge configuration writes as red. 4. For amber/red operations, use the helper to build the request shape, explain the target and expected effect, and stop for explicit operator approval before sending the emitted `httpRequest` through the gateway. 5. Include the target light, grouped light, room, scene, behavior, bridge id, action, and expected physical effect in approval text. 6. Never paste the Hue application key, OAuth client secret, or remote token into chat. The helper emits `secretHeaders` or `<secret:...>` placeholders for gateway-side resolution. 7. Hue Bridge certificates are self-signed by default. The helper marks local bridge HTTPS requests with a scoped `allowSelfSignedTls` flag for the gateway `http_request` proxy. Do not use a blanket insecure TLS bypass. 8. If a live call returns `401` or `unauthorized...