agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-google-tv-streamer/SKILL.md

gadget-google-tv-streamer

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

Control Google TV Streamer media through Google Cast or remote keys and app links through Android TV Remote v2 using Muse Home Link. Use the currently available service and normal Remote v2 pairing; not a generic Google TV device skill.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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 Google TV Streamer advertises a usable Cast receiver and/or Android TV Remote v2 service.

    line 11
  2. Distinctive:

    Keep Cast and Remote v2 endpoints distinct.

    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 necessary, start normal user-approved pairing, complete the displayed code challenge and retain the client certificate/private key.

    line 30
  5. Distinctive:

    After authenticated connection, send the requested documented remote key or app link using the compatible client.

    line 31
  6. Distinctive:

    Keep discovery, pairing success and remote-control success as separate outcomes.

    line 36
  7. Distinctive:

    No screenshots, package queries/installation, battery/screen inspection, developer/debugging setup or fallback control.

    line 41
  8. Distinctive:

    No universal foreground-app query, app entitlement or off-state wake promise.

    line 42

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

Google TV Streamer

Use this skill when the confirmed Google TV Streamer advertises a usable Cast receiver and/or Android TV Remote v2 service.

Identify the Device

  • Match Google TV Streamer model identity and current firmware/service metadata rather than assuming every Google TV device is this model.
  • Keep Cast and Remote v2 endpoints distinct. Availability of one does not prove the other has paired or can control the device.

Prerequisites

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

  • An already-provisioned device with the relevant interface available.
  • For Remote v2, a compatible androidtvremote2 client, the normal on-screen pairing code and securely retained client certificate/private key.
  • For media playback, a user-approved source the receiver can already reach.

Workflow

  1. For Cast media, volume and status, use the Google Cast skill, including receiver capabilities and result checks.
  2. For Remote v2, use the confirmed service and the client's documented pairing/control connection setup over HomeLink TCP. Do not treat an open control port as a paired session.
  3. If necessary, start normal user-approved pairing, complete the displayed code challenge and retain the client certificate/private key. Pairing and control are separate connections.
  4. After authenticated connection, send the requested documented remote key or app link using the compatible client. Use supported power/volume behavior only when exposed by this device.
  5. Observe available state and ask for visual confirmation where navigation has no reliable programmatic read-back.

Verify the Result

  • Keep discovery, pairing success and remote-control success as separate outcomes.
  • For Cast, follow the shared skill and do not count an app launch or buffering state as playback.

Limits

  • No screenshots, package queries/installation, battery/screen inspection, developer/debugging setup or fallback control.
  • No universal foreground-app query, app entitlement or off-state wake promise.

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.