selkies/skills/xterm/SKILL.md
Lightweight X11 terminal emulator (xterm) that triggers on-demand XWayland on labwc/selkies-desktop, enabling X11 automation tools (xdotool, xprop, xwininfo) to find windows. Use when working with xterm, on-demand XWayland startup, or X11-based window automation on a Wayland desktop.
npx skillsauth add overthinkos/overthink-plugins xtermInstall 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.
Lightweight X11 terminal emulator. On labwc (selkies-desktop), launching xterm triggers XWayland to start on-demand, enabling X11-based automation tools (xdotool, xprop, xwininfo) to find windows.
rpm:
packages:
- xterm
| Property | Value |
|----------|-------|
| Depends | None |
| Packages | xterm |
| WM_CLASS | xterm / XTerm |
| XWayland | Triggers on-demand start on labwc |
Drive xterm through the wl: verb's methods (run with charly check live <image> --filter wl):
wl: exec — launch xterm (triggers XWayland)wl: focus — focus by app_idwl: xprop — query X11 propertieswl: geometry — get window position/sizewl: close — close windowImportant: The wl: exec verb sets DISPLAY=:0 automatically for X11 apps.
labwc has XWayland compiled in (+xwayland) but starts it on-demand only when an X11 client opens. Without an X11 app like xterm:
wl: scroll method (xdotool click 4/5) and the wl: drag method (xdotool mousedown/mouseup) can't target X11 windowsWith xterm installed, users can launch it to enable full XWayland testing.
selkies-desktop metalayer/charly-selkies:selkies-labwc (via selkies-desktop metalayer)/charly-selkies:selkies-labwc-nvidia (via selkies-desktop metalayer)/charly-check:wl — the wl: verb's exec / focus / close / xprop / geometry methods/charly-selkies:selkies-desktop-layer — Desktop metalayer that includes this candy/charly-image:layer — candy authoring reference (charly.yml schema, task verbs, service declarations)/charly-check:check — declarative testing (check: block, charly check box, charly check 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).