agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-lg-webos-tvs/SKILL.md

gadget-lg-webos-tvs

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

Control supported LG webOS TV inputs, apps, audio, and remote functions through Muse Home Link. Use normal local SSAP WebSocket pairing; route Cast media to the shared Google Cast skill only if a separate receiver is 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

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 a confirmed LG webOS display exposes its local SSAP WebSocket 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:

    Read available system, power, audio, input and application information.

    line 29
  4. Distinctive:

    If an independent Cast receiver is advertised and the user wants its media controls, follow the Google Cast skill.

    line 32
  5. Distinctive:

    Check SSAP success/error responses and the specific state affected, not merely WebSocket connectivity.

    line 36
  6. Distinctive:

    Do not equate Cast app status with the TV's input or all foreground-app state.

    line 37
  7. Distinctive:

    No UDP wake, silent pairing bypass, cloud alternative or assumed inbound media server.

    line 41
  8. Distinctive:

    No arbitrary device configuration, software installation or screenshot path.

    line 43

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

LG webOS TVs

Use this skill when a confirmed LG webOS display exposes its local SSAP WebSocket service.

Identify the Device

  • Confirm exact model/webOS version and the discovered WebSocket endpoint; capabilities vary by model and firmware.
  • A DIAL advertisement is not proof of Cast. Only use the Cast path when current firmware independently advertises a Cast receiver.

Prerequisites

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

  • An already-configured display and a compatible SSAP client such as bscpylgtv using HomeLink TCP/WebSocket access.
  • Normal on-screen approval for the client registration when needed; store the returned client key securely and reuse it.
  • User permission for the requested input, app, audio, notification or remote operation.

Workflow

  1. Connect and register using the normal SSAP pairing flow, preserving the configured TLS trust and stored client key. A rejected/canceled prompt is not authorization.
  2. Read available system, power, audio, input and application information. Select actual returned input/app IDs rather than guessing.
  3. Issue the requested supported SSAP control: audio/mute, input selection, installed-app launch, notification or remote action. If a pointer/button socket URL is returned, validate its host and obtain authorization for a changed destination before opening it.
  4. Monitor SSAP responses/subscriptions or read state again. For keys/notifications lacking full feedback, report the limitation.
  5. If an independent Cast receiver is advertised and the user wants its media controls, follow the Google Cast skill; apply its receiver capability checks and do not duplicate its procedure.

Verify the Result

  • Check SSAP success/error responses and the specific state affected, not merely WebSocket connectivity.
  • Do not equate Cast app status with the TV's input or all foreground-app state.

Limits

  • No UDP wake, silent pairing bypass, cloud alternative or assumed inbound media server.
  • Standby availability and installed apps vary by model. An unreachable sleeping TV cannot be promised a local wake through this skill.
  • No arbitrary device configuration, software installation or screenshot path.

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.