agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-roborock-vacuums/SKILL.md

gadget-roborock-vacuums

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

Read status and send supported cleaning, pause, or dock commands to compatible Roborock vacuums through Muse Home Link. Use python-roborock's encrypted local TCP channel with existing credentials; not Mi Home UDP miIO or A01 wet/dry devices.

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 confirmed Roborock-app-compatible vacuum supports the local channel described by python-roborock and its existing …

    line 11
  2. Distinctive:

    Use the current local endpoint.

    line 16
  3. Very specific:

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

    line 20
  4. Distinctive:

    Read the model's supported status, battery, current mission and errors.

    line 29
  5. Distinctive:

    Check that status reflects the requested mission.

    line 35
  6. Distinctive:

    No cloud account/bootstrap, map retrieval, room-map setup or cloud-dependent station functions in this skill.

    line 41
  7. Distinctive:

    Do not assume every Roborock generation supports the same local protocol.

    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

Roborock Vacuums

Use this skill when the confirmed Roborock-app-compatible vacuum supports the local channel described by python-roborock and its existing local credentials are available.

Identify the Device

  • Confirm model, firmware, device UID and local protocol compatibility; do not select this skill solely from a Roborock vendor label.
  • Use the current local endpoint. The community client's local channel uses TCP 58867; this is different from the UDP miIO path used by some Mi Home devices.

Prerequisites

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

  • Existing local key and device identity supplied securely, plus the model information needed by the compatible client.
  • A local-only python-roborock channel or equivalent encrypted implementation routed through HomeLink. Disable or omit cloud bootstrap/fallback paths.
  • Permission for the requested robot movement and a safe, prepared cleaning area.

Workflow

  1. Initialize the documented local channel with the current host, local key and device UID. Preserve protocol negotiation, message framing/encryption, sequence correlation and keepalive behavior.
  2. Read the model's supported status, battery, current mission and errors. Use its vacuum command model, not an unrelated A01 wet/dry appliance protocol.
  3. For a requested operation, send the documented local cleaning, pause or return-to-dock command supported by this model.
  4. Correlate the response and poll/subscribe to fresh state as supported. If local communication fails, report it rather than quietly switching to a cloud channel.

Verify the Result

  • Check that status reflects the requested mission; acknowledgment alone does not prove movement or completion.
  • Returning to dock is not the same as docked/charging. Report faults or blocked movement without automatic retries.
  • Inspect state before repeating a command after an uncertain response.

Limits

  • No cloud account/bootstrap, map retrieval, room-map setup or cloud-dependent station functions in this skill.
  • Mi Home UDP miIO and A01 wet/dry devices are not interchangeable with this vacuum path.
  • Do not assume every Roborock generation supports the same local protocol.

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