agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-vizio-d40f-g9/SKILL.md

gadget-vizio-d40f-g9

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

Control supported VIZIO D40f-G9 TV functions through paired local SmartCast HTTPS using Muse Home Link. Use the shared Google Cast skill for media only when a separate Cast receiver is actually advertised.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 VIZIO D40f-G9 exposes a compatible SmartCast local management service.

    line 11
  2. Very specific:

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

    line 20
  3. Distinctive:

    Use the documented SmartCast pairing challenge/PIN flow with the user, or reuse valid stored credentials.

    line 28
  4. Distinctive:

    Read available power, input, app and remote-control state using the model-compatible client.

    line 29
  5. Distinctive:

    Read state after the action.

    line 31
  6. Distinctive:

    No UDP wake, universal standby access, cloud control, firmware changes or general app installation.

    line 42
  7. Distinctive:

    No duplicate Cast procedure or assumed media hosting.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

VIZIO D40f-G9

Use this skill when the confirmed VIZIO D40f-G9 exposes a compatible SmartCast local management service.

Identify the Device

  • Confirm exact model and firmware from existing device information and the current service endpoint.
  • VIZIO SmartCast management and Google Cast are different interfaces. A SmartCast product name alone does not prove a currently available Cast receiver.

Prerequisites

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

  • An already-configured TV and a compatible pyvizio client over HomeLink HTTPS.
  • Normal on-screen PIN pairing when required, secure storage of the returned authentication token, and appropriate device-specific TLS trust.
  • Permission for the requested TV operation; media playback also requires a suitable receiver-reachable source.

Workflow

  1. Use the documented SmartCast pairing challenge/PIN flow with the user, or reuse valid stored credentials. Do not bypass the pairing prompt.
  2. Read available power, input, app and remote-control state using the model-compatible client. Resolve IDs from device responses.
  3. Perform the requested supported input/app/remote action and retain API result/error information. Do not assume a generic endpoint works on every firmware.
  4. Read state after the action. If the TV is in a standby mode that disables its network API, report that limitation.
  5. For an independently advertised Cast receiver, follow the Google Cast skill for media/status/volume; keep its sessions and verification distinct from SmartCast management.

Verify the Result

  • Confirm token-authorized access and the resulting TV state separately.
  • A remote-key acknowledgment may need visual confirmation; it does not prove successful navigation.
  • A Cast load is successful only under the shared skill's playback checks.

Limits

  • No UDP wake, universal standby access, cloud control, firmware changes or general app installation.
  • No duplicate Cast procedure or assumed media hosting.

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.