selkies/skills/selkies-desktop-nvidia/SKILL.md
GPU-accelerated Selkies streaming desktop with NVIDIA CUDA. Use when working with the selkies-desktop-nvidia image.
npx skillsauth add overthinkos/overthink-plugins selkies-desktop-nvidiaInstall 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.
GPU-accelerated variant of selkies-desktop using the NVIDIA base image with CUDA toolkit.
selkies-desktop-nvidia:
base: nvidia
layers:
- agent-forwarding
- selkies-desktop
- dbus
- ov
ports:
- "3000:3000"
- "9222:9222"
- "9224:9224"
platforms:
- linux/amd64
agent-forwarding (gnupg + direnv + ssh-client) + selkies-desktop metalayer (pipewire + chrome + labwc + waybar-labwc + desktop-fonts + swaync + pavucontrol + wl-tools + wl-screenshot-pixelflux + wl-overlay + wl-record-pixelflux + a11y-tools + xterm + tmux + asciinema + fastfetch + selkies) + dbus + ov
| Port | Service | |------|---------| | 3000 | Selkies web UI (Traefik HTTPS → static files + WebSocket proxy) | | 9222 | Chrome DevTools Protocol (CDP, via socat relay) | | 9224 | Chrome DevTools MCP (Streamable HTTP) |
chrome-data → ~/.chrome-debug (Chrome profile)selkies-config → ~/.config/selkiesnvidia — Fedora 43 + RPM Fusion + CUDA toolkit + NVIDIA drivers.
Same layers, but on a GPU base that includes the full CUDA toolkit. Use a GPU
variant for GPU-accelerated H.264 encoding. The CPU sibling selkies-desktop
runs on the cachyos base. There are two GPU siblings: this selkies-desktop-nvidia
on the Fedora nvidia base, and cachyos.selkies-desktop-nvidia in the
overthinkos/cachyos submodule, built on the CachyOS GPU base (cachyos.nvidia)
with build: [pac, aur]. See /ov-distros:cachyos.
Desktop video recording included via wl-record-pixelflux (part of selkies-desktop metalayer). With NVIDIA GPU, pixelflux-record may use NVENC for H.264 encoding (zero CPU overhead).
Not yet tested. The CPU variant (selkies-desktop, cachyos base) works with CPU encoding. This variant needs verification for NVENC hardware encoding.
/ov-selkies:selkies-desktop — full Selkies streaming desktop metalayer/ov-distros:nvidia — GPU runtime and CDI device auto-detection (base)/ov-distros:cuda — CUDA toolkit and libraries (via nvidia base)/ov-infrastructure:dbus-layer — session bus for desktop services/ov-tools:ov — in-container ov binary (enables ov eval dbus notify)/ov-distros:agent-forwarding — SSH/GPG/direnv agent forwardingcachyos.selkies-desktop-nvidia is the CachyOS GPU sibling (built on the cachyos.nvidia GPU base, build: [pac, aur]) in the overthinkos/cachyos submodule. See /ov-distros:cachyos./ov-selkies:selkies-desktop — CPU-encoding sibling on cachyos/ov-openclaw:openclaw-desktop — the CachyOS/CPU all-in-one: this streaming desktop stack + the openclaw-full gateway + AI CLIs + a CPU ollama + the full ov toolchain (ov-full + container-nesting + golang + gh). Use it if you want to build images / start nested pods / launch VMs from inside the browser-accessible desktop./ov-selkies:selkies-desktop-bootc — bootable VM flavor/ov-distros:nvidia — parent base image with CUDA toolkit/ov-eval:eval — parent router for live-container verbs (ov eval cdp|wl|dbus|vnc|mcp)/ov-eval:cdp — drive Chrome inside the streaming desktop/ov-eval:wl — interact with the labwc Wayland session/ov-eval:dbus — D-Bus notifications via in-container ov binary/ov-build:ov-mcp-cmd — inherits chrome-devtools-mcp's 2 deploy-scope mcp: checks; use ov eval mcp list-tools selkies-desktop-nvidia to verify the MCP server is alive and exposing the full tool catalog./ov-image:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)/ov-build:build — build.yml vocabulary (distros, builders, init-systems)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).