Philips Hue Connector for Muse
Control Philips Hue lights locally: list lights and rooms, set brightness/color, activate scenes, read sensors.
- What
- Control Philips Hue lights locally: list lights and rooms, set brightness/color, activate scenes, read sensors.
- Cost
- Free
- Needs
- A Philips Hue Bridge on your LAN, paired once via its physical link button (no cloud key needed) — the application key is kept in your Muse's secure vault (never paste secrets here). Note: every write acts on the physical home — confirm the exact light/room and change first; reading needs no confirmation. Local API works on the same LAN only; off-network, use the remote OAuth path.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that controls your Philips Hue setup over the local Hue CLIP v2 API: list lights and rooms, set light state (on/off, brightness, color), set room-level grouped lights, activate scenes, and read motion, temperature, and light-level sensors. Every write acts on the physical home — confirm the exact light/room and the change first (whole-home changes need explicit confirmation); reading needs none. Pair once with the bridge's physical link button — no cloud key needed; the local API works on the same LAN, or remotely via the Hue Remote API (OAuth). Free — requires a Hue Bridge. Draft: written from Philips Hue's public CLIP v2 docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Quick answer
Philips Hue Connector for Muse is a free Muse skill that controls Philips Hue setup over the Hue CLIP v2 API, listing lights and rooms, setting brightness and color, activating scenes, and reading sensors. Every write acts on the home, so confirm the light or room and the change, and pairing once with the bridge button needs no cloud key.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 6e31fd4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: A Philips Hue Bridge on your LAN, paired once via its physical link button (no cloud key needed) — the application key is kept in your Muse's secure vault (never paste secrets here). Note: every write acts on the physical home — confirm the exact light/room and change first; reading needs no confirmation. Local API works on the same LAN only; off-network, use the remote OAuth path. No GitHub account needed unless listed here. Install "Philips Hue Connector for Muse" for me. A Muse agent skill that controls your Philips Hue lights locally: list lights and rooms, set brightness/color, activate scenes, read sensors. Repository: https://github.com/bluman1/muse-connectors/tree/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/philips-hue Pinned version: install the code at commit 6e31fd44a71f9f28377a1460e64cd7483c3cce22 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "philips-hue". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. pair my Hue Bridge and save the application key in the vault). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 6e31fd4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.