agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-apple-homepod-mini/SKILL.md

gadget-apple-homepod-mini

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

Control HomePod mini volume, supported existing-session playback, and output groups through Muse Home Link. Use when the requested speaker exposes compatible local pyatv services; not for starting new audio streams.

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

8 rules. About 0 are common, 4 are distinctive, and 4 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.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when fresh discovery identifies a HomePod mini, commonly model identifier AudioAccessory5,1, with a compatible local control …

    line 11
  2. Distinctive:

    Use pyatv device information and feature availability as the capability boundary.

    line 16
  3. Very specific:

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

    line 20
  4. Very specific:

    Read device_info, feature availability, volume and available output-device/session state.

    line 29
  5. Distinctive:

    Read volume and the relevant session/group state after an action.

    line 36
  6. Distinctive:

    Do not infer that a stereo pair can be created or dismantled through the output-device API.

    line 37
  7. Distinctive:

    No general RAOP/UDP audio streaming, media hosting on Link, signed-in Mac automation, Siri/Intercom, Home configuration or …

    line 41
  8. Very specific:

    Do not recommend play_url for this device.

    line 42

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

Apple HomePod mini

Use this skill when fresh discovery identifies a HomePod mini, commonly model identifier AudioAccessory5,1, with a compatible local control service.

Identify the Device

  • Match model identity, current AirPlay/RAOP service endpoints and the intended speaker or existing stereo-pair primary.
  • Use pyatv device information and feature availability as the capability boundary. A service advertisement alone does not prove every control is available.

Prerequisites

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

  • A compatible pyatv client with its control sockets routed over HomeLink, using discovery already supplied by Link rather than agent-side multicast.
  • Honor the speaker's existing access/password/pairing requirements and preserve any credentials and session encryption. Do not weaken access settings to obtain a connection.
  • Permission for the requested audio action and its target speakers.

Workflow

  1. Construct the client configuration from the current device identity and supported service endpoints. Connect only the local TCP control paths needed for the operation.
  2. Read device_info, feature availability, volume and available output-device/session state. Unavailable during idle is different from permanently unsupported.
  3. For a requested volume change, use the supported volume setter or step operation with the documented scale, then read volume back. Some firmware has acknowledged a setter without changing the level.
  4. For transport controls, check that the existing session exposes the requested play/pause/next/previous capability. Do not assume this client can inspect or control all playback started elsewhere.
  5. For a requested group change, use supported output-device operations with explicitly identified existing receiver IDs and confirm group membership afterward. Group changes can affect other rooms and are not part of discovery.

Verify the Result

  • Read volume and the relevant session/group state after an action. Report unavailable metadata honestly.
  • Do not infer that a stereo pair can be created or dismantled through the output-device API.

Limits

  • No general RAOP/UDP audio streaming, media hosting on Link, signed-in Mac automation, Siri/Intercom, Home configuration or temperature/humidity access is promised.
  • Do not recommend play_url for this device. Playback control of a supported existing session is distinct from creating a new media stream.
  • Other HomePod generations and third-party AirPlay receivers 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.

Check your setup, free