agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-dyson-pure-hot-cool-hp04/SKILL.md

gadget-dyson-pure-hot-cool-hp04

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

Read Dyson Pure Hot+Cool HP04 status and operate supported fan or heating controls through Muse Home Link. Use only with a compatible local MQTT interface and existing device credentials.

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, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 confirmed device is a Dyson Pure Hot+Cool HP04 and compatible local MQTT credentials are already available.

    line 11
  2. Distinctive:

    Use the device's current MQTT 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:

    Read available fan, airflow, oscillation, heating and environmental state through the client's model-specific properties.

    line 29
  5. Distinctive:

    Wait for and inspect the subsequent state update.

    line 31
  6. Distinctive:

    Treat sensor readings as device measurements, not a guarantee of room-wide air quality or temperature.

    line 37
  7. Distinctive:

    No cloud credential retrieval, account login, firmware changes or universal Dyson-family support in this runtime path.

    line 41

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

Dyson Pure Hot+Cool HP04

Use this skill when the confirmed device is a Dyson Pure Hot+Cool HP04 and compatible local MQTT credentials are already available.

Identify the Device

  • Confirm HP04 identity and the product type required by the compatible libdyson device class.
  • Use the device's current MQTT endpoint. An open MQTT port or Dyson MAC prefix is not proof that authentication or this model's commands work.

Prerequisites

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

  • Existing device serial, product type and local MQTT password/credential in approved secret storage.
  • A model-compatible libdyson client using HomeLink's TCP connection. Initialize it with the supplied local values rather than invoking account/cloud discovery.
  • User permission for changes, especially heating mode or temperature.

Workflow

  1. Connect the HP04-compatible local client, authenticate and subscribe to the model's status topics before requesting its current state.
  2. Read available fan, airflow, oscillation, heating and environmental state through the client's model-specific properties. Keep units and missing/stale sensor values explicit.
  3. For the requested change, call the matching documented HP04 operation, such as fan power/speed, supported oscillation or heating target. Respect device ranges and modes; do not send guessed generic MQTT payloads.
  4. Wait for and inspect the subsequent state update. Preserve device thermal protections and any mode restrictions.

Verify the Result

  • Authentication success is separate from receiving fresh state.
  • Confirm the changed property in a new state message; a publish acknowledgment is not an appliance acknowledgment.
  • Treat sensor readings as device measurements, not a guarantee of room-wide air quality or temperature.

Limits

  • No cloud credential retrieval, account login, firmware changes or universal Dyson-family support in this runtime path.
  • An unavailable key or incompatible product type is a setup blocker, not a reason to brute-force credentials or use unauthenticated fallback.

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.