agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-meross-smart-plugs/SKILL.md

gadget-meross-smart-plugs

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

Read status and switch compatible Meross smart plugs through Muse Home Link. Use the signed local HTTP interface with an existing device UUID and key; not cloud key acquisition or generic HomeKit onboarding.

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

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

  • 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 Meross plug and firmware support the signed local HTTP interface and its existing device key is available.

    line 11
  2. Very specific:

    Use the discovered local HTTP service and documented /config 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:

    Do not infer power consumption from relay state, or promise metering unless the device advertises and documents that feature.

    line 36
  5. Distinctive:

    No universal Meross model support, arbitrary namespace writes, firmware updates or separate HomeKit onboarding procedure.

    line 41

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

Meross Smart Plugs

Use this skill when the exact Meross plug and firmware support the signed local HTTP interface and its existing device key is available.

Identify the Device

  • Confirm the device UUID, model and firmware; a Meross vendor label alone is insufficient.
  • Use the discovered local HTTP service and documented /config endpoint. HomeKit-branded variants must still be checked for this interface.

Prerequisites

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

  • The device UUID and existing local key, supplied through approved secret storage.
  • A direct protocol client or an agent-authored implementation of the documented request envelope. Use the community implementation as a protocol reference; installing its host platform is not required.
  • Permission to switch the actual load attached to the plug.

Workflow

  1. Send a signed read for Appliance.System.All and, where supported, Appliance.System.Ability. Use the protocol's message ID, timestamp, namespace, method, device context and signature exactly as documented.
  2. Inspect reported abilities and current channel states. A device may expose Appliance.Control.ToggleX, an older toggle namespace or another model-specific interface; choose what it actually supports.
  3. For a requested relay change, send the documented SET for that namespace and channel with the desired on/off value. Do not guess a channel or reuse an unrelated model's payload.
  4. Validate the matching response, method/error information and message identity, then read state again using the supported namespace.

Verify the Result

  • A transport success or signed acknowledgment does not prove relay state. Compare a fresh state response with the requested channel/value.
  • Do not infer power consumption from relay state, or promise metering unless the device advertises and documents that feature.

Limits

  • Cloud account/key acquisition is not part of this runtime skill. Stop for missing credentials; do not reset or re-pair the plug.
  • No universal Meross model support, arbitrary namespace writes, firmware updates or separate HomeKit onboarding procedure.

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