agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-tuya-wifi-devices/SKILL.md

gadget-tuya-wifi-devices

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

Read status and control mapped capabilities on compatible Tuya local-TCP devices through Muse Home Link. Use only with a known protocol version, device ID, local key, and exact datapoint schema; prefer a matching device-specific skill.

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

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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 device is confirmed to support Tuya local TCP and its protocol, key and model-specific datapoint map are …

    line 11
  2. Distinctive:

    Do not infer device type or protocol version from a manufacturer prefix or discovery ports 6666/6667.

    line 16
  3. Distinctive:

    Prefer a specific skill where available, such as compatible eufy RoboVacs.

    line 17
  4. Very specific:

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

    line 21
  5. Distinctive:

    Read current status and map each returned datapoint through the known schema, including data type, units, range and enumeration values.

    line 30
  6. Distinctive:

    Read fresh state afterward and compare the mapped value.

    line 32
  7. Distinctive:

    If the key no longer works, stop for updated authorized credentials rather than re-pairing automatically.

    line 38
  8. Distinctive:

    Not all Tuya-branded devices expose this interface.

    line 42
  9. Distinctive:

    No cloud wizard/login, key extraction, automatic re-pairing, arbitrary raw datapoint writes or firmware changes.

    line 43
  10. Distinctive:

    Do not generalize a protocol version or datapoint schema across unrelated models.

    line 44

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

Tuya Wi-Fi Devices

Use this skill when the exact device is confirmed to support Tuya local TCP and its protocol, key and model-specific datapoint map are known.

Identify the Device

  • Confirm device ID, model, firmware and protocol version from existing approved configuration/documentation.
  • Do not infer device type or protocol version from a manufacturer prefix or discovery ports 6666/6667. The control endpoint is separate, commonly TCP 6668, and must be confirmed.
  • Prefer a specific skill where available, such as compatible eufy RoboVacs.

Prerequisites

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

  • Existing device ID, local key, protocol version and a trustworthy model/firmware datapoint schema, supplied securely.
  • A compatible TinyTuya client with local TCP transport routed through HomeLink.
  • Permission for the specific actuator/load. A raw datapoint's existence does not establish its meaning or authorize writing it.

Workflow

  1. Initialize the appropriate local device class using the confirmed identity, current endpoint, existing local key and explicit protocol version. Do not run a cloud setup wizard as part of control.
  2. Read current status and map each returned datapoint through the known schema, including data type, units, range and enumeration values.
  3. For a requested change, write only the mapped datapoint and valid desired value using the compatible client. Do not assume datapoint 1 is always an on/off switch.
  4. Read fresh state afterward and compare the mapped value. Handle protocol errors, unavailable datapoints and optimistic devices explicitly.

Verify the Result

  • An encrypted connection or write acknowledgment is not proof of the intended physical result.
  • Report unknown datapoints as unknown; never discover their purpose by trial-and-error writes.
  • If the key no longer works, stop for updated authorized credentials rather than re-pairing automatically.

Limits

  • Not all Tuya-branded devices expose this interface; battery devices, gateways and new firmware can differ.
  • No cloud wizard/login, key extraction, automatic re-pairing, arbitrary raw datapoint writes or firmware changes.
  • Do not generalize a protocol version or datapoint schema across unrelated models.

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.