agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-google-pixel-tablet/SKILL.md

gadget-google-pixel-tablet

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

Play supported Cast media and control playback or volume on Google Pixel Tablet through Muse Home Link. Use the shared Google Cast skill only while the tablet exposes its receiver in supported docked, locked Hub Mode.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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 current discovery identifies the Google Pixel Tablet with its Cast receiver currently available.

    line 11
  2. Very specific:

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

    line 21
  3. Distinctive:

    Use the Google Cast skill for discovery interpretation, receiver/media status, playback controls, volume, media loading and verification.

    line 28
  4. Distinctive:

    Follow the shared skill's operation-specific checks and report whether the result was actually observed on this device.

    line 34
  5. Distinctive:

    No arbitrary undocked casting, battery/screen inspection, screenshots, general tablet automation, private setup routes or device …

    line 38
  6. Distinctive:

    Do not infer device administration or general remote-control capabilities from Cast support.

    line 39

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

Use this skill when current discovery identifies the Google Pixel Tablet with its Cast receiver currently available.

Identify the Device

  • Confirm Pixel Tablet model metadata and a currently advertised receiver. The tablet being on Wi-Fi is not sufficient.
  • Match the current receiver to the user's intended device; use its current service endpoint, not a remembered address.
  • The tablet must be in its supported docked, locked Hub Mode with Cast reception enabled. Check current availability; do not assume undocked or unlocked operation.

Prerequisites

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

  • The device is already provisioned and available as a receiver in its supported operating state.
  • For new playback, an existing user-authorized media source must be reachable by the receiver. Device access alone does not supply media hosting.

Workflow

  1. Use the Google Cast skill for discovery interpretation, receiver/media status, playback controls, volume, media loading and verification. That skill is the single protocol procedure.
  2. Apply this profile's model and operating-state restrictions before selecting an operation. Missing media status while idle is not proof that the device is unreachable.
  3. For an existing group, follow the shared skill's separate group-target rules and confirm that the user intended all group members.

Verify the Result

  • Follow the shared skill's operation-specific checks and report whether the result was actually observed on this device.

Limits

  • No arbitrary undocked casting, battery/screen inspection, screenshots, general tablet automation, private setup routes or device configuration.
  • Do not infer device administration or general remote-control capabilities from Cast support.

Sources

  • Shared Google Cast skill and protocol 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