Google TV Streamer

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 an already-provisioned Google TV Streamer with the relevant interface available, and, for Remote v2, a compatible androidtvremote2 client, the normal on-screen pairing code and a securely retained client certificate/private key, and, for media playback, a user-approved source the receiver can already reach. Its Cast part also depends on the companion gadget-google-cast skill (see step 2). Installing the file configures none of that. Install "Google TV Streamer" for me. It controls Google TV Streamer media through Google Cast, or remote keys and app links through Android TV Remote v2, using Muse Home Link; it is not a generic Google TV device skill. It matches Google TV Streamer model identity and current firmware/service metadata rather than assuming every Google TV device is this model, and it keeps Cast and Remote v2 endpoints distinct — availability of one does not prove the other has paired or can control the device. For Cast media, volume and status it uses the shared Google Cast skill at ../gadget-google-cast/SKILL.md, including receiver capabilities and result checks. For Remote v2 it uses the confirmed service and the compatible androidtvremote2 client's documented pairing/control connection setup over HomeLink TCP; an open control port is not treated as a paired session. If necessary it starts normal user-approved pairing, completes the displayed code challenge and retains the client certificate/private key securely — pairing and control are separate connections. After an authenticated connection it sends the requested documented remote key or app link, using supported power/volume behaviour only when exposed by this device. It observes available state and asks for visual confirmation where navigation has no reliable programmatic read-back. Discovery, pairing success and remote-control success are kept as separate outcomes, and for Cast an app launch or a buffering state is not counted as playback. Limits: no screenshots, package queries or installation, battery or screen inspection, developer or debugging setup, or fallback control; no universal foreground-app query, app entitlement or off-state wake promise. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-google-tv-streamer/ 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-tv-streamer/ 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 1e1f0428686943bb5c6568f012dc37b057cb1a9fb52de09afa2acc41c15b9fc0 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,545 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 TV Streamer, through two distinct local interfaces: Google Cast and Android TV Remote v2, which are never inferred from each other. - Dependency (Cast part only): for Cast media, volume and status this skill uses the shared Google Cast skill — it points to ../gadget-google-cast/SKILL.md, and the Cast procedure itself is not in this file. Install this folder under the exact name "gadget-google-tv-streamer" 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 Cast use. This install copies only this profile's folder: do not copy the companion into this install. The Android TV Remote v2 procedure, by contrast, is described in this SKILL.md itself. - 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 media is loaded during installation. - At use time, exchanges go only to my local Google TV Streamer: Cast exchanges follow the shared Cast procedure, and Remote v2 exchanges go over the documented pairing/control connections through HomeLink TCP with the compatible androidtvremote2 client. Pairing happens only with my approval, using the normal on-screen code, and the client certificate/private key are retained securely; pairing and control are separate connections, and an open control port alone is never treated as a paired session. - The skill does not do screenshots, package queries or installation, battery/screen inspection, developer/debugging setup or fallback control, and it promises no universal foreground-app query, app entitlement or off-state wake. Discovery, pairing success and remote-control success are reported as separate outcomes, and an app launch or buffering state is never counted as Cast playback. - 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-tv-streamer folder into the agent's skills directory, in a folder named exactly "gadget-google-tv-streamer", 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-tv-streamer), 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 TV Streamer already provisioned on my local network with the relevant interface available; for Remote v2, pair normally with the on-screen code and keep the client certificate/private key stored securely; for media, provide a user-approved source the receiver can already reach; and install the companion gadget-google-cast skill separately (same repo, same pinned commit) for complete Cast use, since 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.