ov-layers/skills/wl-screenshot-grim/SKILL.md
# wl-screenshot-grim - Screenshot via grim (wlr-screencopy) ## Overview Provides `grim` for Wayland screenshot capture using the `wlr-screencopy` protocol. Works on sway and standalone wlroots compositors. **Does NOT work on selkies-desktop** (labwc nested in pixelflux can't deliver screencopy frames). For selkies-desktop, use `wl-screenshot-pixelflux` instead. ## Layer Definition ```yaml rpm: packages: - grim ``` ## Key Properties | Property | Value | |----------|-------| | Depends
npx skillsauth add overthinkos/overthink-plugins ov-layers/skills/wl-screenshot-grimInstall 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.
Provides grim for Wayland screenshot capture using the wlr-screencopy protocol. Works on sway and standalone wlroots compositors. Does NOT work on selkies-desktop (labwc nested in pixelflux can't deliver screencopy frames).
For selkies-desktop, use wl-screenshot-pixelflux instead.
rpm:
packages:
- grim
| Property | Value |
|----------|-------|
| Depends | None |
| Packages | grim |
| Protocol | wlr-screencopy-unstable-v1, ext-image-copy-capture-v1 |
Used by ov test wl screenshot — auto-detected when grim is available in the container.
ov test wl screenshot <image> [output.png]
sway-desktop metalayer/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:wl — ov test wl screenshot auto-detects grim/ov-layers:wl-screenshot-pixelflux — Alternative for selkies-desktop/ov-layers:wl-tools — Companion layer (input, window mgmt, clipboard)/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)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).