ov-layers/skills/wl-overlay/SKILL.md
Wayland overlay windows via gtk4-layer-shell (for screen recordings). Use when working with the wl-overlay layer, gtk4-layer-shell, or overlay dependencies.
npx skillsauth add overthinkos/overthink-plugins wl-overlayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | dbus |
| Install files | tasks:, ov-overlay |
gtk4 (RPM)gtk4-layer-shell (RPM) — includes Gtk4LayerShell-1.0.typelib for GObject Introspectionpython3-gobject (RPM)ov-overlayInstalled to ~/.local/bin/ov-overlay via tasks:. Dual-mode script (daemon + client) using GTK4 + gtk4-layer-shell for layer-shell protocol overlays.
Key implementation details:
#!/usr/bin/python3 (system Python 3.14, NOT pixi's Python — PyGObject is an RPM package)CDLL("libgtk4-layer-shell.so.0") must load before GTK4 import (registers layer-shell protocol before Wayland display init). Uses versioned soname .so.0 (unversioned .so is in -devel package only)window { background: none; } CSS applied globally at daemon startup. Without this, GTK4 on Wayland creates opaque surfaces that don't support alpha transparencyGtk.DrawingArea + Cairo paint(). GTK4 CSS background-color with rgba() does not composite correctly on layer-shell windowsGLib.idle_add()/tmp/ov-overlay.sock with JSON-line protocolOVERLAY (above TOP where waybar/swaync live)NONE (overlays never capture input)-1 (don't push other windows)ov-overlay-<name> per overlay window# image.yml — typically included via desktop metalayers
# Already part of sway-desktop, selkies-desktop, niri-desktop
my-desktop:
layers:
- wl-overlay
ov test wl overlay show my-image --type text --text "Hello" --name intro
ov test wl overlay list my-image
ov test wl overlay hide my-image --all
/ov-layers:sway-desktop — sway desktop composition/ov-layers:selkies-desktop — selkies streaming desktop composition/ov-layers:niri-desktop — niri desktop composition/ov-images:sway-browser-vnc (via sway-desktop metalayer)/ov-images:openclaw-sway-browser (via sway-desktop metalayer)/ov-images:openclaw-ollama-sway-browser (via sway-desktop metalayer)/ov-images:selkies-desktop (via selkies-desktop metalayer)/ov-images:selkies-desktop-nvidia (via selkies-desktop metalayer)/ov-layers:dbus — D-Bus session bus (dependency, required by GTK4)/ov-layers:wl-tools — Wayland automation tools (sibling in desktop stack)/ov-layers:a11y-tools — also uses python3-gobject (RPM deduplication handles overlap)/ov-layers:tmux — tmux (required for overlay daemon hosting)/ov:wl-overlay — Overlay command usage, types, recording workflow/ov:wl — Compositor-agnostic desktop automation/ov:record — Recording commands (overlays compose with recording)/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.