agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-philips-hue-bridges/SKILL.md

gadget-philips-hue-bridges

Skill2.6k starsChanged 25 days agoApache-2.0View on GitHub

Control lights, brightness, and existing room, zone, or scene actions through a Philips Hue CLIP v2 bridge using Muse Home Link. Use a local application key or normal physical-button pairing; excludes legacy BSB001.

1 other project uses a version of this, 1 of them edited.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 13 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the facebookincubator/muse-gadget-sdk repository that our weekly crawl found: only 14 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about facebookincubator/muse-gadget-sdk

The biggest 5 of 14 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 14

Talked about on GitHub, Bluesky and Hacker News (14 times).

On GitHub · 11

6 more on GitHub

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when fresh discovery identifies a Hue bridge exposing CLIP v2 and the user requests lights, brightness or an existing scene.

    line 11
  2. Very specific:

    Read bridge model/API information, such as /api/0/config, after host authorization.

    line 16
  3. Very specific:

    Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.

    line 21
  4. Distinctive:

    Use an existing local application key or obtain one with the user's physical bridge-button approval.

    line 23
  5. Very specific:

    Read the target light's on/dimming/color capability fields and connectivity.

    line 31
  6. Very specific:

    PUT /clip/v2/resource/light/<id> with a minimal body such as {"on":{"on":true}} or {"dimming":{"brightness":40}}.

    line 32
  7. Distinctive:

    No UDP Entertainment streaming, cloud discovery, automatic firmware updates, group creation or automation editing in this skill.

    line 44
  8. Distinctive:

    Check capabilities separately for Bridge Pro and each bulb.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Philips Hue Bridges: Local Light and Scene Control

Use this skill when fresh discovery identifies a Hue bridge exposing CLIP v2 and the user requests lights, brightness or an existing scene.

Identify the Device

  • Match a Hue bridge, not an individual Zigbee bulb. _hue._tcp and bridge metadata can identify the current endpoint.
  • Read bridge model/API information, such as /api/0/config, after host authorization. Confirm CLIP v2 support on the square BSB002 bridge.
  • Round BSB001 uses a different legacy API and is not covered by this recipe.

Prerequisites

Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.

  • Use an existing local application key or obtain one with the user's physical bridge-button approval. An account/cloud discovery service is not required.
  • For pairing, POST a documented devicetype to /api while the link-button window is open and securely store the returned username/application key. Do not log it.
  • Validate the bridge's TLS identity using a configured/pinned bridge trust path; do not disable certificate validation globally.

Workflow

  1. Send the stored key in the hue-application-key header through a credential-aware client, never as a credential-bearing shell command.
  2. GET /clip/v2/resource/light, /room, /zone and /scene as needed. Resolve resource IDs from current responses and disambiguate names before writes.
  3. Read the target light's on/dimming/color capability fields and connectivity. Only send fields the device actually supports.
  4. PUT /clip/v2/resource/light/<id> with a minimal body such as {"on":{"on":true}} or {"dimming":{"brightness":40}}. Brightness is percent; honor the reported minimum. Color temperature, when requested and supported, uses the reported mirek_schema range.
  5. For an existing room/zone, resolve its grouped_light service before a group write. For an existing scene, PUT /clip/v2/resource/scene/<id> with {"recall":{"action":"active"}}. Confirm the affected group is intended.
  6. Inspect both response data and errors, then poll the affected lights after transitions. Group broadcasts can miss an individual bulb.

Verify the Result

  • Confirm resulting per-light state, not only a group response or scene acknowledgement.
  • For a group where every lamp must change, identify any straggler and re-read before an individually scoped correction.
  • A scene may contain multiple intended states; compare to its actions rather than assuming every member should be on.

Limits

  • No UDP Entertainment streaming, cloud discovery, automatic firmware updates, group creation or automation editing in this skill.
  • Check capabilities separately for Bridge Pro and each bulb. Unsupported effects remain unsupported.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.