Google Home Max

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 the Google Home Max already provisioned and available as a Cast receiver in its supported operating state, and, for new playback, an existing user-authorized media source that the receiver can reach (device access alone does not supply media hosting). No credential is required by this Cast profile, but its whole Cast procedure lives in the companion gadget-google-cast skill (see step 2). Installing the file configures none of that. Install "Google Home Max" for me. It plays audio and controls playback or volume on a Google Home Max through Muse Home Link, using its available Cast receiver and the shared Google Cast skill; it does not provide general auxiliary-input control. It matches Google Home Max model metadata and its current receiver identity — existing groups are separate targets from the individual speaker — and it uses the receiver's current service endpoint, not a remembered address. This is an audio-only receiver: Cast support does not establish local control over its physical auxiliary input or all input-switching behaviour. This profile contains no Cast procedure of its own: its workflow step 1 delegates discovery interpretation, receiver/media status, playback controls, volume, media loading and verification to the shared Google Cast skill at ../gadget-google-cast/SKILL.md, which is the single protocol procedure (Cast v2, through a documented client such as PyChromecast over Home Link). This profile's model and operating-state restrictions are applied before selecting an operation. Missing media status while idle is not proof that the device is unreachable. For an existing group, the shared skill's separate group-target rules are followed and the user confirms they intended all group members. Verification follows the shared skill's operation-specific checks, and the report says whether the result was actually observed on this device. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-google-home-max/ 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-google-home-max/ 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 5e40ccebfc3b02de3123b57c1fde6a263a00b9b3091661bc595b1d94cafeffd1 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,121 bytes). There is no script, no code and no configuration in it; at use time it works through Muse Home Link against my own local Google Home Max as a Cast receiver, under this profile's model and operating-state restrictions. - Dependency: this profile delegates its whole Cast procedure to the shared Google Cast skill — its step 1 points to ../gadget-google-cast/SKILL.md, and this profile alone does not contain the Cast procedure. Install this folder under the exact name "gadget-google-home-max" so the relative link resolves if the companion is installed alongside it, and install the companion gadget-google-cast skill (separate listing, same repo, same pinned commit) for complete use. This install, however, copies only this profile's folder: do not copy the companion into this install. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No receiver is contacted, no pairing is started and no media is loaded during installation. - At use time, exchanges go only to my local Google Home Max as a Cast receiver, at its current advertised endpoint, following the shared Cast procedure. No credential is required by this Cast profile: ordinary local Cast control needs no sender account or pairing code, and for new playback the receiver itself fetches an existing user-authorized media source that it can reach — private media is never uploaded just to make it castable. - The skill does not create groups, does not assume arbitrary input control, and does not use private setup-token routes. It does not infer device administration or general remote-control capabilities from Cast support, and Cast support gives it no control over the physical auxiliary input. - 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-google-home-max folder into the agent's skills directory, in a folder named exactly "gadget-google-home-max", 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-google-home-max), 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 Google Home Max already provisioned on my local network and available as a Cast receiver in its supported operating state; and install the companion gadget-google-cast skill separately (same repo, same pinned commit) for complete use, because this profile delegates its whole Cast procedure to it and this install copies only this profile's folder, not the companion; 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.