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

gadget-tplink-kasa-ep25

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

Control relay, LED, and supported auto-off settings or read energy measurements on TP-Link Kasa EP25 through Muse Home Link. Use the confirmed SMART local protocol and approved credentials, not EP10 legacy XOR.

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 fresh discovery identifies a compatible Kasa EP25 and the user requests switching, energy readings or supported …

    line 11
  2. Very specific:

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

    line 20
  3. Very specific:

    Use turn_on/turn_off for requested relay changes.

    line 29
  4. Distinctive:

    Read the energy module/features for actual power and totals, preserving their reported units.

    line 30
  5. Distinctive:

    No reset, re-keying, Wi-Fi changes or firmware updates.

    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 EP25: Authenticated Switching and Energy Readings

Use this skill when fresh discovery identifies a compatible Kasa EP25 and the user requests switching, energy readings or supported auto-off.

Identify the Device

  • Confirm EP25 model, hardware/firmware, protocol family, encryption/login version and local service endpoint from available discovery metadata and authenticated device information.
  • This path uses SMART local authentication, not EP10 legacy XOR. A port alone does not identify KLAP/AES or login version.

Prerequisites

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

  • Provide the device's approved TP-Link local-authentication credentials or supported stored credential hash through secure storage. These authenticate locally; no cloud-control login is part of the runtime flow.
  • Know what load is attached. If credentials or the protocol configuration are missing, request setup instead of guessing or resetting.

Workflow

  1. Configure python-kasa for the known SMART device/transport and exact discovered endpoint; use HomeLink network routing instead of the library's broadcast discovery.
  2. Authenticate and update device state. Read supported features before invoking a capability; keep raw feature dumps private because they can include setup codes.
  3. Use turn_on/turn_off for requested relay changes. LED and auto-off features are separate operations; change them only when explicitly requested and exposed by this device.
  4. Read the energy module/features for actual power and totals, preserving their reported units. Availability differs across firmware.
  5. For auto-off, use the actual auto_off_enabled and auto_off_minutes features if present; read back both. Do not treat unsupported schedule APIs as equivalent.
  6. Refresh after each action and inspect authentication/device errors separately from connection failures.

Verify the Result

  • Confirm resulting relay/LED state and requested auto-off settings.
  • Report measured consumption with units; a working relay is not proof that the attached appliance is drawing power.

Limits

  • The SMART path does not support the legacy schedule module. Do not add schedules or use cloud/Matter/Home automation fallbacks.
  • No reset, re-keying, Wi-Fi changes or firmware updates. Other Kasa/Tapo products require their own capability checks.

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.