agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-elgato-key-light/SKILL.md

gadget-elgato-key-light

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

Control Elgato Key Light power, brightness, white temperature, and requested identification through Muse Home Link. Use with the local HTTP light API; the documented device is board type 53, not other light variants.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 an Elgato Key Light and the user requests its light controls.

    line 11
  2. Very specific:

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

    line 21
  3. Very specific:

    PUT /elgato/lights with {"numberOfLights":1,"lights":[{"on":1}]} for on, or on:0 for off.

    line 29
  4. Very specific:

    If explicitly asked to identify the panel, POST /elgato/identify once.

    line 32
  5. Very specific:

    Check actual on/brightness/temperature values after a write.

    line 37
  6. Distinctive:

    No power-on configuration, rename, restart or firmware-update operations under this light-control skill.

    line 43
  7. Distinctive:

    Do not expose this unauthenticated API outside the trusted network or infer color/RGB support from a white-temperature panel.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Elgato Key Light: Power, Brightness and White Temperature

Use this skill when fresh discovery identifies an Elgato Key Light and the user requests its light controls.

Identify the Device

  • Match _elg._tcp with manufacturer Elgato and model/board metadata; the usual API port is 9123, but use the discovered port.
  • GET /elgato/accessory-info and confirm productName, hardwareBoardType 53 and lights capability. Keep serial/MAC/network metadata private.
  • Air, Mini and Light Strip are distinct variants; their additional capabilities are outside this skill.

Prerequisites

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

  • The light must already be on Wi-Fi. The local HTTP API is unauthenticated; that does not waive host/action authorization.
  • Confirm the requested lighting change will not unexpectedly disrupt a call, recording or live stream.

Workflow

  1. GET /elgato/lights and read numberOfLights plus the target light's current on, brightness and temperature.
  2. PUT /elgato/lights with {"numberOfLights":1,"lights":[{"on":1}]} for on, or on:0 for off; send only requested fields.
  3. For brightness, send brightness as an integer percent within the supported range; 3–100 is the useful range for board type 53, while 0–2 may have no visible effect. Use on:0 for off.
  4. For white temperature, send mireds: round(1000000 / kelvin), clamped to 143–344 for board 53. For example, 4000 K is 250 mireds; smaller values are cooler.
  5. If explicitly asked to identify the panel, POST /elgato/identify once; it visibly blinks and may return an empty body.
  6. Poll /elgato/lights to read back changes; serialize requests rather than simulating fades with rapid bursts.

Verify the Result

  • Check actual on/brightness/temperature values after a write; convert units clearly.
  • An empty successful identify response is expected, but visible identification still needs observation.
  • Restore temporary identification settings when appropriate to the request.

Limits

  • No power-on configuration, rename, restart or firmware-update operations under this light-control skill.
  • Do not expose this unauthenticated API outside the trusted network or infer color/RGB support from a white-temperature panel.

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.

Check your setup, free