ov-selkies/skills/wl-overlay-layer/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
my-desktop:
layers:
- wl-overlay
ov eval wl overlay show my-image --type text --text "Hello" --name intro
ov eval wl overlay list my-image
ov eval wl overlay hide my-image --all
/ov-selkies:sway-desktop — sway desktop composition/ov-selkies:selkies-desktop — selkies streaming desktop composition/ov-selkies:sway-browser-vnc (via sway-desktop metalayer)/ov-openclaw:openclaw-sway-browser (via sway-desktop metalayer)/ov-openclaw:openclaw-ollama-sway-browser (via sway-desktop metalayer)/ov-selkies:selkies-desktop (via selkies-desktop metalayer)/ov-selkies:selkies-desktop-nvidia (via selkies-desktop metalayer)/ov-foundation:dbus — D-Bus session bus (dependency, required by GTK4)/ov-selkies:wl-tools — Wayland automation tools (sibling in desktop stack)/ov-selkies:a11y-tools — also uses python3-gobject (RPM deduplication handles overlap)/ov-foundation:tmux — tmux (required for overlay daemon hosting)/ov-advanced:wl-overlay — Overlay command usage, types, recording workflow/ov-advanced:wl — Compositor-agnostic desktop automation/ov-advanced:record — Recording commands (overlays compose with recording)/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).