selkies/skills/selkies-kde-nvidia/SKILL.md
The NVIDIA-GPU build of the KDE Plasma Selkies streaming desktop — full Plasma nested in pixelflux with REAL NVENC (cuda-arch-builder-compiled). MUST be invoked before building, deploying, or troubleshooting the selkies-kde-nvidia box.
npx skillsauth add overthinkos/overthink-plugins selkies-kde-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.
The NVIDIA-GPU build of the KDE Plasma flavor (/charly-selkies:selkies-kde) —
the same headless-pod KDE streaming desktop on the CachyOS GPU base
(cachyos.nvidia), with pixelflux's real NVENC encoder compiled in. It is the
KDE sibling of /charly-selkies:selkies-labwc-nvidia (labwc + NVENC); both use
builder.pixi: arch.cuda-arch-builder so the selkies candy's build.sh compiles
pixelflux's real nvenc-sys encoder (the stock arch-builder has no CUDA → an
NVENC stub).
Owned by the overthinkos/cachyos submodule (box/cachyos).
selkies-kde-nvidia:
base: nvidia # the CachyOS GPU base (cachyos.nvidia)
build: [pac, aur]
builder: {pixi: arch.cuda-arch-builder} # nvcc + ffnvcodec headers → real NVENC
candy:
- agent-forwarding
- selkies-kde-desktop
- dbus
- charly
port: ["3000:3000", "9222:9222", "9224:9224", "2222:2222"]
platform: [linux/amd64]
The box carries a build-scope check: check pixelflux-nvenc-compiled that
greps the built pixelflux .so for NvEncodeAPICreateInstance (the NVENC SDK
entry point the nvenc-sys crate binds). The stub build patches nvenc-sys out
of pixelflux's Cargo.toml, so the symbol is absent → the check FAILS on a
non-NVENC build. This is the regression-proof for the box's NVENC functionality
(identical to /charly-selkies:selkies-labwc-nvidia).
Same ports as /charly-selkies:selkies-kde (3000/9222/9224/2222). Encoder: real NVENC
on the passed-through NVIDIA GPU (CDI --device nvidia.com/gpu=all); falls back to
x264 when the GPU is unavailable.
charly -C box/cachyos box build selkies-kde-nvidia
charly check box selkies-kde-nvidia # build-scope incl. pixelflux-nvenc-compiled
NVENC at runtime requires a passed-through NVIDIA GPU — proven on the
check-selkies-kde-nvidia-vm bed (a requires_exclusive: [nvidia-gpu] passthrough
VM that asserts real NVENC frame production; the preemption arbiter frees the GPU
from any running holder). See /charly-internals:disposable + /charly-check:check.
/charly-selkies:selkies-kde — the cpu/default sibling (shared definition + the KDE flavor framing)./charly-selkies:selkies-labwc-nvidia — the labwc + NVENC sibling (same cuda-arch-builder + NVENC-compile proof)./charly-selkies:selkies-kde-desktop — the KDE metalayer + the de-SDDM headless-Plasma design./charly-distros:cachyos — the CachyOS GPU base (cachyos.nvidia) + submodule./charly-distros:nvidia, /charly-distros:cuda — the GPU runtime + CUDA toolkit candies./charly-image:image — image family umbrella (candy: image entries with base:/from:, build/validate/inspect/list)./charly-build:build — the embedded build 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).