agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-irobot-roomba-braava/SKILL.md

gadget-irobot-roomba-braava

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

Read status and send supported cleaning, pause, resume, or dock commands to compatible Wi-Fi Roomba/Braava robots through Muse Home Link. Use documented local MQTT/TLS with existing BLID and password, not cloud credential retrieval.

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

4 rules. About 0 are common, 3 are distinctive, and 1 is 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.

  • 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 exact Wi-Fi Roomba or Braava model and firmware support the documented local protocol.

    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:

    No cloud credential retrieval, UDP discovery from the agent, new provisioning or universal support for all Roomba/Braava models.

    line 41
  4. Distinctive:

    Do not bypass physical, battery, bin or safety conditions.

    line 43

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

iRobot Roomba and Braava

Use this skill when the exact Wi-Fi Roomba or Braava model and firmware support the documented local protocol.

Identify the Device

  • Confirm the robot model, firmware and protocol compatibility, then use its current local endpoint.
  • The presence of TCP 8883 is not sufficient to identify an iRobot or prove local control.

Prerequisites

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

  • The robot's existing BLID and local password in approved secret storage.
  • A compatible dorita980 local client or equivalent MQTT/TLS implementation routed through HomeLink; retain device-specific TLS handling.
  • A commissioned robot and explicit permission for a cleaning, pause or dock action, with the area safe for movement.

Workflow

  1. Instantiate the client's local interface with the current endpoint, BLID, password and appropriate protocol version. Do not invoke cloud login or credential-discovery helpers.
  2. Authenticate and subscribe to the supported state feed. Read mission/cleaning state, battery, docking and reported errors before any command.
  3. Send only the model's documented requested cleaning, pause, resume or return-to-dock command. Check whether the current mission state requires a particular sequence rather than issuing generic commands blindly.
  4. Monitor fresh mission state and errors, and release the local session when finished. Avoid competing sessions if the robot reports a connection conflict.

Verify the Result

  • Confirm the robot's reported mission changed, not merely that MQTT accepted a message.
  • Distinguish returning to base from docked/charging and paused from completed cleaning.
  • Resolve uncertain delivery by reading state before issuing another movement command.

Limits

  • No cloud credential retrieval, UDP discovery from the agent, new provisioning or universal support for all Roomba/Braava models.
  • Room maps, targeted jobs, mop/water controls and station functions are outside scope unless documented for the exact model and already configured.
  • Do not bypass physical, battery, bin or safety conditions.

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.