Philips Hue Bridges

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have an existing local Hue application key, or a new one obtained with my physical bridge-button approval (POST a documented devicetype to /api while the link-button window is open, then store the returned username/application key securely and never log it). Installing the file configures none of that. Install "Philips Hue Bridges" for me. It controls lights through a Philips Hue bridge on my local network, nothing else. After fresh discovery confirms a square BSB002 bridge exposing CLIP v2 (the round legacy BSB001 uses a different API and is not covered), it GETs /clip/v2/resource/light, /room, /zone and /scene over local HTTPS, resolving resource IDs from current responses and disambiguating names before any write. It reads each target light's on/dimming/colour capabilities and connectivity and only sends supported fields: PUT /clip/v2/resource/light/<id> with a minimal body such as {"on":{"on":true}} or {"dimming":{"brightness":40}} (brightness is a percent, honouring the reported minimum; colour temperature uses the reported mirek_schema range). For a room or zone it resolves the grouped_light service first; for an existing scene it PUTs /clip/v2/resource/scene/<id> with {"recall":{"action":"active"}}. It inspects response data and errors, then polls the affected lights, because a group broadcast can miss a bulb. Limits: no UDP Entertainment streaming, no cloud discovery, no automatic firmware updates, no group creation, no automation editing; Bridge Pro and each bulb are checked separately. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-philips-hue-bridges/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-philips-hue-bridges/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 e8fac4d5732f13eb553b746ed1a74c65655ad054c7f3deb60826498314198df8 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (3,240 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local Hue bridge (BSB002, CLIP v2 over HTTPS). It has no dependency on any other gadget skill in this lot. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my local Hue bridge: the stored application key is sent in the hue-application-key header through a credential-aware client, never as a credential-bearing shell command and never logged. Pairing, only with my physical bridge-button approval, POSTs a documented devicetype to /api while the link-button window is open and stores the returned key securely. The bridge's TLS identity is validated through a configured/pinned trust path; certificate validation is never disabled globally. - The skill does not do cloud discovery, UDP Entertainment streaming, automatic firmware updates, group creation or automation editing, and it does not cover the legacy round BSB001 bridge. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-philips-hue-bridges folder into the agent's skills directory, in a folder named exactly "gadget-philips-hue-bridges", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-philips-hue-bridges), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have a square BSB002 Hue bridge already set up on my local network; and either reuse my existing local application key from approved secret storage or approve pairing physically at the bridge button, knowing the returned key is stored securely and never logged; using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.