decompile-tv-lib
Skill1.2k starsChanged 5 days agoGPL-3.0View on GitHub
Read the TV's own closed, stripped native libraries — libplayerAPIs (StarfishMediaAPIs), libpf (the media pipeline), libAcbAPI, libcbe (the Chromium media stack), the DILE/VPQ layers — by harvesting them off the device and decompiling them locally with Ghidra. Use when a question can only be answered by what the firmware actually DOES: which JSON keys a Load payload parser accepts and at what path, what an enum→string table contains, what a struct's field layout is, whether a symbol that exists is reachable from the mode we run in, or why a call that "should" work does nothing. Also use before binding any new FFI into a TV library, as the evidence half of `bind-tv-lib-abi` — that skill requires offsets and symbol behaviour to be PROVEN, and this is how you prove them. Reach for it instead of guessing from a symbol name, a header found online, or another client's source: those tell you what some firmware does, not what THIS one does.
- Installs packages
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about GLinnik21/plx-native
- @michaelmclean.me“Dude reverse engineered an LG TV so he could rewrite the Plex app in Rust Went from 30 seconds of booting …”Bluesky · Oct 8, 2026 · 7 likes
- webosbrew/apps-repo“Add FinNative (io.github.tiper.finnative)”GitHub · Nov 7, 2026
- webosbrew/apps-repo“Add Butaca, a native Jellyfin client for LG webOS”GitHub · Nov 6, 2026
- GLinnik21/plxnative-huds“Build and publish initial 1.0 HUD resource bundles”GitHub · Nov 3, 2026
- chris-ritsen/samsung-tv-root“Untethered root proven: boot-time .NET agent self-roots on Q60B (T-NKLBAKUC), no host controller needed”GitHub · Oct 9, 2026
The biggest 5 of 8 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 8
Talked about on GitHub and Bluesky (8 times).
On GitHub · 7
- Nov 7, 2026Add FinNative (io.github.tiper.finnative) — webosbrew/apps-repo0 reactions · 1 comment
- Nov 6, 2026Add Butaca, a native Jellyfin client for LG webOS — webosbrew/apps-repo0 reactions · 1 comment
- Nov 3, 2026Build and publish initial 1.0 HUD resource bundles — GLinnik21/plxnative-huds0 reactions
- Oct 9, 2026Untethered root proven: boot-time .NET agent self-roots on Q60B (T-NKLBAKUC), no host controller needed — chris-ritsen/samsung-tv-root0 reactions · 4 comments
- Sep 27, 2026Simplify the About page: fork of plx-native, link to our GitHub for licenses — gnacho/butaca0 reactions · 1 comment
2 more on GitHub
- Sep 21, 2026fix(ui): brand the jellyfin flavor's visible strings as Butaca — gnacho/butaca0 reactions
- Aug 4, 2026Add PlxNative — native Plex client for LG webOS — webosbrew/apps-repo0 reactions · 17 comments
On Bluesky · 1
- Oct 8, 2026Dude reverse engineered an LG TV so he could rewrite the Plex app in Rust Went from 30 seconds of booting to just 3 seconds lmfao… — @michaelmclean.me7 likes and reposts
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bind-tv-lib-abiSkill
- crash-triageSkill
- cut-releaseSkill
- fleet-planSkill
- land-prSkill
- profile-tvSkill
- setup-environmentSkill
- tv-lockSkill
- tv-sessionSkill
- ui-simSkill
- wake-tvSkill
- which-tierSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.

