Freebox Player Pop

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have a confirmed Freebox Player Pop (not the Freebox router/server) already set up on my local network with the requested interface enabled and available, and, for Remote v2, a compatible androidtvremote2 client routed through HomeLink, a persistent client certificate/private key preserved securely and my normal on-screen pairing code, or, for Cast, a suitable existing media source reachable by the receiver and the companion gadget-google-cast skill for the Cast procedure (see step 2). Installing the file configures none of that. Install "Freebox Player Pop" for me. It controls Freebox Player Pop media through Google Cast or remote keys and app links through Android TV Remote v2, through Muse Home Link, using whichever local service is actually available; it is not for the Freebox router/server. Player Pop identity and firmware are confirmed — a Freebox router/server is not the Player Pop — and Cast and Remote v2 are treated as separate services with separate capabilities; neither is inferred from the presence of the other. The player is already set up and the requested interface is enabled and available. For media, status and volume through Cast, it follows the shared Google Cast skill (gadget-google-cast, ../gadget-google-cast/SKILL.md), applying the player's current format, application and standby limitations, and uses the shared skill separately for Cast result verification. For local remote control, it selects the current Remote v2 endpoint and checks the installed client's documented pairing/control service configuration — pairing and control use distinct connections — using a compatible androidtvremote2 client routed through HomeLink, a persistent client certificate/private key and my normal on-screen pairing code: if credentials are absent, it initiates normal Remote v2 pairing with me, I enter the displayed code and the resulting certificate/private-key identity is securely preserved, never regenerated on every connection. It opens the authenticated control connection and sends 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. It uses the available remote-state updates or my confirmation to assess the result: a successful pairing is not proof of remote-command success, and an accepted key is not proof of the intended screen outcome, and the correct player/session is verified 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. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-freebox-player-pop/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-freebox-player-pop/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 5d6f0000589ab3e77ac0e178e3ff677e93bed0d7703dde02d14be6978338d574 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (2 783 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local device. - Cross-reference: for media, status and volume through Cast, this skill delegates to the shared Google Cast skill (gadget-google-cast, ../gadget-google-cast/SKILL.md), a separate lot 1 listing from the same repo at the same pin. Installed alone, this folder keeps a relative link to that companion; the exact folder name gadget-freebox-player-pop keeps that link resolvable when the companion is installed alongside it, and installing the companion is recommended for the Cast part. The tested installation of this listing is still the copy of this skill's own folder only. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my local Freebox Player Pop: either the shared Google Cast procedure (gadget-google-cast) for media/status/volume, or the authenticated Remote v2 control connection via androidtvremote2 for the requested remote key or documented app link, with my persistent client certificate/private key kept securely and my on-screen pairing code used only for normal pairing. No router/server control happens at use time. - The skill does not do screenshots, package management, private setup endpoints, developer/debugging setup or fallback commands, does not claim Cast wakes the player or that every firmware exposes all Remote v2 features, and does not control the Freebox router/server. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-freebox-player-pop folder into the agent's skills directory, in a folder named exactly "gadget-freebox-player-pop", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-freebox-player-pop), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have a confirmed Freebox Player Pop already set up on my local network (not the Freebox router/server); for Remote v2, keep my persistent client certificate/private key securely and be ready to enter the on-screen pairing code; for Cast, have the companion gadget-google-cast skill installed for the Cast procedure; using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.