agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-sonos-speakers/SKILL.md

gadget-sonos-speakers

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

Control Sonos playback, volume, mute, and speaker grouping through Muse Home Link. Use when the intended speaker exposes compatible local UPnP services; resolve the room and group coordinator before acting.

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

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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 fresh discovery identifies a Sonos speaker with a compatible local UPnP service.

    line 11
  2. Distinctive:

    Read the advertised device description and service/control URLs to confirm model, player identity and supported services.

    line 15
  3. Distinctive:

    Read zone/group topology and resolve the requested room, stereo pair and current group coordinator.

    line 16
  4. Very specific:

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

    line 20
  5. Distinctive:

    Read current transport state, track/media information, volume/mute and group membership using the documented service actions.

    line 28
  6. Distinctive:

    Read back volume/mute and group membership.

    line 37
  7. Distinctive:

    If a request times out, inspect current state before replaying a queue/group action.

    line 38
  8. Distinctive:

    No inbound GENA callback server, on-Link media/TTS server, private port-1443 requirement or cloud fallback.

    line 42
  9. Distinctive:

    No account/service provisioning, firmware updates or stereo/home-theater reconfiguration.

    line 44

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

Sonos Speakers

Use this skill when fresh discovery identifies a Sonos speaker with a compatible local UPnP service.

Identify the Device

  • Read the advertised device description and service/control URLs to confirm model, player identity and supported services.
  • Read zone/group topology and resolve the requested room, stereo pair and current group coordinator. Do not equate every network endpoint with a separately controllable room.

Prerequisites

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

  • A compatible SoCo client or SOAP implementation using the actual device service URLs through HomeLink.
  • Permission for the requested room/group and operation; grouping can interrupt or redirect audio in other rooms.
  • For a new media item, an existing URL reachable by the speaker with the needed format and authorization. Do not upload private media or create a server implicitly.

Workflow

  1. Read current transport state, track/media information, volume/mute and group membership using the documented service actions.
  2. For volume/mute, target the intended speaker/room or an explicitly requested group operation. Do not assume a per-speaker volume command changes every group member.
  3. For playback, address the appropriate group coordinator and use the supported play/pause/stop/seek or existing queue action. Changing transport URI or queue contents is a separate user-authorized action.
  4. For a group change, resolve the current coordinator and all intended room IDs, then use the documented join/unjoin operation. Preserve bonded stereo/home-theater configurations.
  5. Poll transport, rendering and topology state after actions. Use polling rather than relying on device-initiated event callbacks to the agent.

Verify the Result

  • Distinguish accepted URI, buffering, playing and stopped states. Confirm that the expected room/group is actually the target.
  • Read back volume/mute and group membership. Physical audibility may still require user confirmation.
  • If a request times out, inspect current state before replaying a queue/group action.

Limits

  • No inbound GENA callback server, on-Link media/TTS server, private port-1443 requirement or cloud fallback.
  • Model-specific capabilities and firmware differ; check the requested operation against the device's advertised services.
  • No account/service provisioning, firmware updates or stereo/home-theater reconfiguration.

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.