ov-selkies/skills/wf-recorder/SKILL.md
Wayland screen recorder for wlroots compositors. Use when working with the wf-recorder layer.
npx skillsauth add overthinkos/overthink-plugins wf-recorderInstall 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 |
|----------|-------|
| Install files | layer.yml (packages only) |
| Depends | none |
RPM: wf-recorder
Native Wayland screen recorder for wlroots-based compositors (sway, labwc, etc.). Captures frames via the wlr-screencopy protocol and encodes to MP4/MKV using system ffmpeg. Supports audio capture with --audio.
Note: Does NOT work on selkies-desktop — use wl-record-pixelflux instead (labwc nested in pixelflux can't deliver screencopy frames).
# image.yml or layer.yml
layers:
- wf-recorder
# Direct usage (inside container)
wf-recorder -f output.mp4 # Record to MP4
wf-recorder -f output.mp4 --audio # With audio
wf-recorder -f output.mp4 -r 60 # 60fps
# Stop with Ctrl-C
ov eval record# Start recording sway desktop (auto-detects wf-recorder)
ov eval record start sway-browser-vnc -n demo --mode desktop
# Interact with desktop
ov eval wl click sway-browser-vnc 640 360
ov eval record cmd sway-browser-vnc "neofetch" -n demo
# Stop and copy to host
ov eval record stop sway-browser-vnc -n demo -o demo.mp4
sway-desktop metalayer (and all images using sway-desktop-vnc)/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-advanced:record — ov eval record start --mode desktop auto-detects wf-recorder/ov-selkies:wl-record-pixelflux — Alternative for selkies-desktop (pixelflux pipeline)/ov-selkies:wl-screenshot-grim — Screenshot companion (same wlr-screencopy protocol)/ov-selkies:sway-desktop — Parent metalayerUse when the user asks about:
wf-recorder layer/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).