agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-ratgdo-v32-garage-door/SKILL.md

gadget-ratgdo-v32-garage-door

Skill2.8k starsChanged 26 days agoApache-2.0View on GitHub

Read and operate installed ratgdo v32 garage-door, light, and lock entities through Muse Home Link. Use this device-specific skill when ratgdo firmware and capabilities are confirmed; require safe, authorized movement and preserve interlocks.

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

6 rules. About 0 are common, 4 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when current discovery and entity metadata identify an already-installed ratgdo v32 controller, not merely an arbitrary …

    line 11
  2. Very specific:

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

    line 20
  3. Distinctive:

    Read the installed firmware's entity descriptions and current door, movement, lock and obstruction states using its enabled API.

    line 27
  4. Very specific:

    Use only the exposed cover open/close/stop, light or lock operation corresponding to the user's request.

    line 29
  5. Distinctive:

    No retrofit installation, flashing, OTA updates, opener rewiring or safety bypasses.

    line 40
  6. Distinctive:

    Only capabilities present in the installed firmware are supported.

    line 41

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

ratgdo v32 Garage Door Controller

Use this skill when current discovery and entity metadata identify an already-installed ratgdo v32 controller, not merely an arbitrary ESP32.

Identify the Device

  • Confirm ratgdo model, installed firmware version and actual garage-door cover, light, lock and obstruction entities.
  • Record entity IDs from the live API. Web-server paths and identifiers differ by ESPHome version; do not transplant another firmware's URLs.

Prerequisites

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

  • An already commissioned controller attached to a working opener, and credentials for its enabled HTTP or native TCP API.
  • An explicit requested door/light/lock action. Confirm the intended door and that movement is safe; preserve all opener interlocks and obstruction protections.

Workflow

  1. Read the installed firmware's entity descriptions and current door, movement, lock and obstruction states using its enabled API. SSE may supply live state over an outbound HTTP connection; the native API can list entities and subscribe over TCP.
  2. For HTTP, construct the entity read/action URL from that firmware's documented web API. For the native API, use a compatible aioesphomeapi client with the device's configured encryption key or credentials.
  3. Use only the exposed cover open/close/stop, light or lock operation corresponding to the user's request. Do not infer position-setting or lock semantics from the entity name alone.
  4. Monitor the door and obstruction states until the requested state is reached or movement stops unexpectedly. If the command result is uncertain, read state before considering any retry.

Verify the Result

  • Distinguish command acceptance, opening/closing and final open/closed states.
  • Report obstruction, unknown position, offline sensors or a lock preventing movement as unresolved; do not override them.
  • A light or lock response must be checked against its entity state, not taken as proof of door movement.

Limits

  • No retrofit installation, flashing, OTA updates, opener rewiring or safety bypasses.
  • Only capabilities present in the installed firmware are supported. Prefer this device skill over the generic ESPHome skill.

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.