agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-eufy-robovac-tuya/SKILL.md

gadget-eufy-robovac-tuya

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

Read status and send basic cleaning or docking commands to compatible Tuya-based eufy RoboVacs through Muse Home Link. Use with a confirmed model schema and existing local key; excludes non-Wi-Fi and AIOT/X10 models.

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 the exact Wi-Fi RoboVac model and firmware are confirmed to use the documented local Tuya interface.

    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 new status and monitor the relevant mission transition.

    line 31
  4. Distinctive:

    Read state before retrying an uncertain movement command.

    line 37
  5. Very specific:

    No AIOT/X10 support, non-Wi-Fi model support, broad room/map/station promises or cloud key retrieval in the runtime path.

    line 41
  6. Distinctive:

    No credential extraction through debugging, provisioning changes or re-pairing.

    line 42

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

eufy RoboVac — Compatible Tuya Models

Use this skill when the exact Wi-Fi RoboVac model and firmware are confirmed to use the documented local Tuya interface.

Identify the Device

  • Confirm the model code, local device ID, protocol and matching datapoint schema; do not use a broad generation table.
  • This is not support for non-Wi-Fi models such as 11S or for X10/AIOT models.

Prerequisites

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

  • Existing local key, device ID and a model-appropriate command/datapoint map supplied securely.
  • A compatible local eufy/TinyTuya client using HomeLink's TCP transport, as described in the Tuya skill.
  • A ready robot and user permission for the intended cleaning or docking action.

Workflow

  1. Initialize the local client with the confirmed model/protocol, current endpoint and supplied credentials. Read state before sending commands.
  2. Decode cleaning mode, battery, error and docking state using the exact model's schema. Do not copy datapoint numbers from a different RoboVac.
  3. For the user's requested action, use the documented clean/start, pause/stop or return-to-dock operation supported by that model.
  4. Read new status and monitor the relevant mission transition. Keep unsupported map, room and station operations out of the command set.

Verify the Result

  • Confirm a reported mission/state change; a TCP or encrypted-packet acknowledgment alone is insufficient.
  • Distinguish a command to dock from successful docking, and report error/battery states without overriding them.
  • Read state before retrying an uncertain movement command.

Limits

  • No AIOT/X10 support, non-Wi-Fi model support, broad room/map/station promises or cloud key retrieval in the runtime path.
  • No credential extraction through debugging, provisioning changes or re-pairing.
  • The existing documented model match and credentials are mandatory; do not write guessed datapoints.

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