agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-tplink-kasa-ep10/SKILL.md

gadget-tplink-kasa-ep10

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

Read status and control relay or LED state on compatible TP-Link Kasa EP10 plugs through Muse Home Link. Use the confirmed legacy IOT local TCP protocol; EP10 has no energy metering and does not use the EP25 authentication path.

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, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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 fresh discovery and a scoped device read confirm a compatible Kasa EP10 and the user requests plug status or switching.

    line 11
  2. Distinctive:

    Use its discovered local TCP 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:

    Use python-kasa's explicitly configured legacy IOT plug client through the shared network access.

    line 27
  5. Very specific:

    Read {"system":{"get_sysinfo":{}}} and retain relay_state and led_off.

    line 29
  6. Distinctive:

    If a response is uncertain, read state before retrying.

    line 37
  7. Distinctive:

    No reset, network changes, credential updates, schedules or firmware actions.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

TP-Link Kasa EP10: Relay and LED Control

Use this skill when fresh discovery and a scoped device read confirm a compatible Kasa EP10 and the user requests plug status or switching.

Identify the Device

  • Confirm exact model, hardware and firmware from legacy system.get_sysinfo, not a vendor prefix or open port.
  • Use its discovered local TCP endpoint; the legacy service commonly uses 9999. Do not run client UDP discovery from the agent.

Prerequisites

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

  • Know the connected load and confirm that switching it is intended.
  • The legacy interface needs no account credentials. If current firmware identifies a different protocol, do not force legacy XOR or silently switch to another family's skill.

Workflow

  1. Use python-kasa's explicitly configured legacy IOT plug client through the shared network access; supply the known endpoint without broadcast discovery.
  2. For an agent-authored transport, legacy TCP frames use a four-byte big-endian payload length and TP-Link's documented XOR-autokey JSON encoding; prefer the maintained implementation over inventing encryption.
  3. Read {"system":{"get_sysinfo":{}}} and retain relay_state and led_off.
  4. Set the relay using system.set_relay_state with state 1 or 0, or the client's turn_on/turn_off. Set system.set_led_off only when an LED change is requested; off:1 disables the LED.
  5. Refresh the device state after each action. Check device error codes, not merely receipt of a TCP frame.

Verify the Result

  • Confirm the desired relay state; LED state is separate and inverted by led_off.
  • A relay acknowledgement does not prove the connected appliance performed its own task.
  • If a response is uncertain, read state before retrying; do not retry with a toggle.

Limits

  • EP10 has no energy meter. Do not promise watts, energy history or EP25 authentication/features.
  • No reset, network changes, credential updates, schedules or firmware actions.

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.