agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-freebox-player-pop/SKILL.md

gadget-freebox-player-pop

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

Control Freebox Player Pop media through Google Cast or remote keys and app links through Android TV Remote v2 using Muse Home Link. Use whichever local service is actually available; not for the Freebox router/server.

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 the confirmed Freebox Player Pop currently exposes a Cast receiver and/or Android TV Remote v2 service.

    line 11
  2. Distinctive:

    Treat Cast and Remote v2 as separate services with separate capabilities.

    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:

    If credentials are absent, initiate normal Remote v2 pairing with the user, enter the displayed code and securely preserve the resulting …

    line 30
  5. Distinctive:

    Use the available remote-state updates or user confirmation to assess the result.

    line 32
  6. Distinctive:

    Verify the correct player/session before changing playback or waking a connected display.

    line 37
  7. Distinctive:

    No screenshots, package management, private setup endpoints, developer/debugging setup or fallback commands.

    line 41
  8. Distinctive:

    No claim that Cast wakes the player or that every Player Pop firmware exposes all Remote v2 features.

    line 42
  9. Distinctive:

    No new media server or automatic app entitlements.

    line 43

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

Freebox Player Pop

Use this skill when the confirmed Freebox Player Pop currently exposes a Cast receiver and/or Android TV Remote v2 service.

Identify the Device

  • Confirm Player Pop identity and firmware. A Freebox router/server is not the Player Pop.
  • Treat Cast and Remote v2 as separate services with separate capabilities; do not infer one from the presence of the other.

Prerequisites

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

  • The player is already set up and the requested interface is enabled and available.
  • For Remote v2, a compatible androidtvremote2 client routed through HomeLink, a persistent client certificate/private key, and the user's normal on-screen pairing code.
  • For Cast playback, a suitable existing media source reachable by the receiver.

Workflow

  1. For media/status/volume through Cast, follow the Google Cast skill; apply the player's current format, application and standby limitations.
  2. For local remote control, select the current Remote v2 endpoint and check the installed client's documented pairing/control service configuration. Pairing and control use distinct connections.
  3. If credentials are absent, initiate normal Remote v2 pairing with the user, enter the displayed code and securely preserve the resulting certificate/private-key identity. Do not regenerate that identity on every connection.
  4. Open the authenticated control connection and send only the requested supported remote key or documented app link using androidtvremote2. App links must target an installed handler and do not constitute package management.
  5. Use the available remote-state updates or user confirmation to assess the result; use the shared skill separately for Cast result verification.

Verify the Result

  • A successful pairing is not proof of remote-command success, and an accepted key is not proof of the intended screen outcome.
  • Verify the correct player/session before changing playback or waking a connected display.

Limits

  • No screenshots, package management, private setup endpoints, developer/debugging setup or fallback commands.
  • No claim that Cast wakes the player or that every Player Pop firmware exposes all Remote v2 features.
  • No new media server or automatic app entitlements.

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