agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-esphome-devices/SKILL.md

gadget-esphome-devices

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

Read and control entities exposed by already-installed ESPHome firmware through Muse Home Link. Use with an enabled native TCP or HTTP API and its configured credentials; prefer the ratgdo skill for ratgdo garage controllers.

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, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the device is confirmed to run ESPHome and already exposes a supported API.

    line 11
  2. Distinctive:

    Use the firmware's service metadata and API information to confirm the device, firmware version and enabled interface.

    line 15
  3. Very specific:

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

    line 20
  4. Distinctive:

    Read sensors or subscribe to state updates over the outbound native connection or HTTP SSE where supported.

    line 29
  5. Distinctive:

    Follow state updates and any action errors.

    line 31
  6. Distinctive:

    Do not retry a toggle, button action or movement command until an uncertain first outcome has been checked.

    line 36
  7. Distinctive:

    No universal entity names or URL templates across firmware versions.

    line 40
  8. Distinctive:

    No firmware installation, OTA, arbitrary device services/scripts, generic Bluetooth proxy, network reconfiguration or safety bypasses.

    line 41

≈ “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

ESPHome Devices

Use this skill when the device is confirmed to run ESPHome and already exposes a supported API; an Espressif manufacturer identifier alone is insufficient.

Identify the Device

  • Use the firmware's service metadata and API information to confirm the device, firmware version and enabled interface.
  • Enumerate live entities and their stable identifiers, types and capabilities. For ratgdo garage controllers, use the more specific ratgdo skill.

Prerequisites

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

  • Already-installed, commissioned firmware with native API or web server enabled.
  • The existing native API encryption key/password or web authentication, if configured, plus a compatible client. Enabling an absent API by reflashing is not part of this skill.

Workflow

  1. Connect to the native API using a compatible aioesphomeapi client and the current endpoint, or use the installed firmware's documented HTTP API. Preserve native session encryption and configured authentication.
  2. List entities, supported commands, ranges and current state. Prefer the native API for structured enumeration when available; web entity IDs and URL conventions are firmware-version dependent.
  3. Read sensors or subscribe to state updates over the outbound native connection or HTTP SSE where supported.
  4. For a requested change, call only the command advertised for that entity: for example a switch's on/off, a light's supported brightness or a cover's supported movement. Convert units and ranges using that entity's metadata.
  5. Follow state updates and any action errors. Distinguish optimistic target states from measured feedback when firmware lacks a physical sensor.

Verify the Result

  • Confirm the intended entity changed and report whether the value is measured, inferred or optimistic.
  • Do not retry a toggle, button action or movement command until an uncertain first outcome has been checked.

Limits

  • No universal entity names or URL templates across firmware versions.
  • No firmware installation, OTA, arbitrary device services/scripts, generic Bluetooth proxy, network reconfiguration or safety bypasses.
  • The entity's existence does not authorize its actuation. Apply the shared physical-action safety rules.

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