Gleb Linnik
Community@GLinnik21
Gleb Linnik maintains skills for building, debugging, verifying, and releasing a native cross-compiled webOS TV application on LG dev televisions.
Agent Skills by Gleb Linnik
Showing 12 vetted skills indexed across 1 GitHub repositories.
GLinnik21setup-environment
Configures the webOS NDK cross-compile toolchain and Rust nightly build environment on macOS.
GLinnik21crash-triage
Diagnose and symbolize fatal signal crashes of a native app on LG webOS televisions.
GLinnik21which-tier
Routes code changes to the cheapest verification tier that can actually detect them.
GLinnik21fleet-plan
Plans parallel agent work across git worktrees with one shared television.
GLinnik21tv-session
Boot, drive, and capture the PlxNative app on an LG webOS television.
GLinnik21tv-lock
Coordinates exclusive access to a shared webOS dev television across concurrent agent lanes.
GLinnik21bind-tv-lib-abi
Verify symbols and struct offsets against device FFmpeg and libcurl binaries before binding them.
GLinnik21profile-tv
Diagnose live PlxNative processes on rooted LG TVs using stack sampling and Mali GPU profiling.
GLinnik21ui-sim
Builds, boots, drives, and screenshots the PlxNative desktop simulator to verify UI changes.
GLinnik21decompile-tv-lib
Decompile stripped ARM32 firmware libraries from LG webOS televisions using Ghidra headless analysis.
GLinnik21wake-tv
Wakes an LG webOS dev TV from standby via Wake-on-LAN and waits for SSH.
GLinnik21cut-release
Automates versioned releases of a webOS app through CI with verification gates.
Frequently Asked Questions About Gleb Linnik
FAQPage SchemaWhat tasks can I accomplish with GLinnik21's webOS TV skills?▼
You can set up the cross-compile toolchain, wake and lock the dev TV, boot and drive the app on-device, triage crashes, profile a janky PlxNative process, decompile LG's closed native libraries, bind new FFmpeg/Starfish FFI symbols, verify changes on the desktop simulator, and cut .ipk releases.
Who are these skills designed for?▼
Engineers and parallel agents developing a native Rust/C++ webOS TV application on a single shared LG dev television. They target developers hitting toolchain errors, on-device crashes, FFI binding work against closed firmware libraries, and anyone coordinating multiple worktree lanes against one physical TV.
How do I verify a change without access to the television?▼
Use the ui-sim skill to build and boot the desktop simulator on macOS or Windows/WSLg, drive it with keys, and capture screenshots. The which-tier skill routes each change to the cheapest verification tier and names which tiers are structurally blind to it.
What prerequisites and dependencies do these skills require?▼
A macOS host with the webOS NDK toolchain, Rust nightly with rust-src, the correct sysroot, and CMake for Sentry Native. On-device work requires a rooted LG webOS dev TV reachable over SSH, Wake-on-LAN for standby recovery, and Ghidra for decompiling harvested firmware libraries.
How do multiple agents share the single dev television safely?▼
The tv-lock skill enforces exclusive possession of the one TV so two jobs never produce plausible wrong data, while fleet-plan decides which parallel worktree lane may request it. Only one lane holds the television at a time; others use the desktop simulator or wait for the lease.