agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-miele-g7566-dishwasher/SKILL.md

gadget-miele-g7566-dishwasher

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

Read local Miele G 7566 dishwasher status through Muse Home Link when its module supports the documented protocol and existing GroupID/GroupKey are available. Consider commands only after confirming exact capabilities and local enablement; remote start is not promised.

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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 a Miele G 7566 has a compatible local communications module and the household's existing GroupID and GroupKey are …

    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 authenticated GET /Devices/ to discover the device route, then the documented local Ident and State resources beneath that route.

    line 29
  4. Distinctive:

    Only consider a command if the exact model/module protocol documents it and current appliance state permits it.

    line 31
  5. Distinctive:

    Keep model identification, successful decryption, readable state and successful physical operation as separate checks.

    line 36
  6. Distinctive:

    No cloud login, key provisioning, reset/recommissioning, generic program writes, new server deployment or bypassed door/remote-start …

    line 44

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

Miele G 7566 Dishwasher

Use this skill when a Miele G 7566 has a compatible local communications module and the household's existing GroupID and GroupKey are available.

Identify the Device

  • Match _mieleathome._tcp discovery and the appliance's model/type metadata. A group identifier is not the secret GroupKey.
  • An unsigned 404 response with a Miele content type can indicate an authentication requirement; it does not prove usable reads or permitted control.

Prerequisites

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

  • Existing GroupID/GroupKey and a client implementing the documented MieleH256 signing, encrypted bodies and authenticated response handling.
  • The exact device route returned by the local appliance API, not a guessed serial number.
  • For any permitted physical command, a user request, a safely prepared appliance and all required panel-side enablement.

Workflow

  1. Implement or use the local-protocol client component described by MieleRESTServer without deploying its REST server. Preserve its signing/encryption rules, exact signed host/path/headers, response validation and secure handling of the GroupKey.
  2. Use authenticated GET /Devices/ to discover the device route, then the documented local Ident and State resources beneath that route. Read only fields actually returned by this module.
  3. Report available status, program, remaining time and faults using the module's documented field meanings. Do not copy cloud-only field names, program lists or filling-level features into the local interface.
  4. Only consider a command if the exact model/module protocol documents it and current appliance state permits it. Remote start is conditional, not promised: the user must prepare/arm the machine locally and all interlocks must allow it.
  5. For an allowed requested operation, use that local protocol's documented command, then poll authenticated state. If the capability or prerequisites cannot be established, remain read-only and explain what is missing.

Verify the Result

  • Keep model identification, successful decryption, readable state and successful physical operation as separate checks.
  • A sleeping module may return stale/invalid information. Do not wake or start it merely to check access without permission.
  • Inspect running/program state after any authorized command; HTTP acceptance alone does not prove start or stop.

Limits

  • Support is conditional on this unit's communications module and exposed capabilities.
  • MieleRESTServer endpoints such as /generate-summary and /start/<name> belong to its wrapper server, not the appliance. Do not send them to the dishwasher.
  • No cloud login, key provisioning, reset/recommissioning, generic program writes, new server deployment or bypassed door/remote-start interlocks.

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.