TP-Link Kasa EP25

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have a compatible Kasa EP25 plug already set up on my local network, confirmed by EP25 model, hardware/firmware, protocol family, encryption/login version and local service endpoint from discovery metadata and authenticated device information (a port alone does not identify KLAP/AES or login version), know what load is attached, and have the device's approved TP-Link local-authentication credentials or a supported stored credential hash in secure storage — these authenticate locally and no cloud-control login is part of the runtime flow; if credentials or the protocol configuration are missing, setup is requested instead of guessing or resetting. Installing the file configures none of that. Install "TP-Link Kasa EP25" for me. It controls relay, LED and supported auto-off settings, or reads energy measurements, on TP-Link Kasa EP25 plugs through Muse Home Link, using the confirmed SMART local protocol and approved credentials — not EP10 legacy XOR. It is used when fresh discovery identifies a compatible EP25: model, hardware/firmware, protocol family, encryption/login version and local service endpoint are confirmed from discovery metadata and authenticated device information, because a port alone does not identify KLAP/AES or login version. It configures python-kasa for the known SMART device/transport and exact discovered endpoint, using HomeLink network routing instead of the library's broadcast discovery, authenticates and updates device state, and reads supported features before invoking a capability, keeping raw feature dumps private because they can include setup codes. It uses turn_on/turn_off for requested relay changes; LED and auto-off are separate operations, changed only when explicitly requested and exposed by this device — for auto-off it uses the actual auto_off_enabled and auto_off_minutes features if present and reads back both, without treating unsupported schedule APIs as equivalent. It reads the energy module/features for actual power and totals, preserving their reported units, knowing availability differs across firmware, refreshes after each action, and inspects authentication/device errors separately from connection failures. It verifies the resulting relay/LED state and requested auto-off settings and reports 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, and there are no schedules, no cloud/Matter/Home automation fallbacks, no reset, no re-keying, no Wi-Fi changes and no firmware updates; other Kasa/Tapo products require their own capability checks. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-tplink-kasa-ep25/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-tplink-kasa-ep25/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 dbcf6592d9b00f90099143976e7762356cabc9f0e083eca53daf99465d984b65 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (2,748 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local device. It has no dependency on any other gadget skill in this lot. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my local Kasa EP25 plug over the authenticated SMART local protocol through python-kasa: local authentication with my approved local-authentication credentials or supported stored credential hash from secure storage, then state/energy reads and requested relay, LED or auto-off writes. No cloud-control login is part of the runtime flow, and raw feature dumps are kept private because they can include setup codes. - The skill does not add schedules through the unsupported legacy schedule module, does not use cloud/Matter/Home automation fallbacks, and does not do resets, re-keying, Wi-Fi changes or firmware updates. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-tplink-kasa-ep25 folder into the agent's skills directory, in a folder named exactly "gadget-tplink-kasa-ep25", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-tplink-kasa-ep25), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have a compatible Kasa EP25 already set up on my local network with its SMART protocol configuration confirmed; know the attached load; and keep the device's approved local-authentication credentials or supported stored credential hash in secure storage (local authentication only, no cloud-control login); using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.