distros/skills/nvidia/SKILL.md
NVIDIA GPU base image with runtime support and CUDA toolkit on Fedora. Base for all GPU-accelerated boxes (python-ml, jupyter, ollama, comfyui). MUST be invoked before building, deploying, configuring, or troubleshooting the nvidia box.
npx skillsauth add overthinkos/overthink-plugins 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.
NVIDIA GPU base image — provides GPU runtime (driver libs, CDI toolkit) and CUDA development toolkit on Fedora.
The nvidia and cuda candies are multi-distro (Fedora rpm + Arch pac), so a
CachyOS GPU base exists alongside this Fedora nvidia box: cachyos.nvidia
(cachyos + agent-forwarding + nvidia + cuda) in the overthinkos/cachyos
submodule. The two are siblings — pick the Fedora nvidia box for the
RPM-based GPU stack, cachyos.nvidia for the Arch/CachyOS GPU stack. See
/charly-distros:cachyos.
| Property | Value | |----------|-------| | Base | fedora-nonfree (fedora + RPM Fusion) | | Layers | agent-forwarding, nvidia, cuda | | Platforms | linux/amd64 | | Registry | ghcr.io/overthinkos |
fedora-nonfree (fedora + rpmfusion — provides RPM Fusion free + nonfree repos)nvidia — GPU runtime: driver libs, nvidia-container-toolkit (CDI), VA-APIcuda — CUDA toolkit, cuDNN, onnxruntime, ffmpeg-libsThe nvidia box lives in the overthinkos/fedora submodule (box/fedora):
charly -C box/fedora box build nvidia
charly shell nvidia
/charly-distros:nvidia — NVIDIA GPU runtime (driver libs, CDI generation via nvidia-ctk)/charly-distros:cuda — CUDA toolkit and GPU development libraries/charly-languages:python-ml — ML Python environment/charly-jupyter:jupyter — Jupyter notebook server/charly-ollama:ollama — LLM inference server/charly-comfyui:comfyui — image generation UI/charly-distros:fedora — parent base (no GPU)/charly-distros:cachyos — cachyos.nvidia is the CachyOS GPU-base sibling (Arch/CachyOS GPU stack)/charly-coder:charly-arch — Arch Linux charly toolchain with nvidia (shared candies)/charly-distros:charly-fedora — Fedora charly toolchain with nvidia (shared candies)After charly box build:
charly shell nvidia -c "nvidia-smi" — GPU infocharly shell nvidia -c "nvidia-ctk --version" — CDI toolkitcharly shell nvidia -c "nvcc --version" — CUDA compilerMUST be invoked when the task involves the nvidia box, GPU base images, CUDA in containers, or CDI device configuration. Invoke this skill BEFORE reading source code or launching Explore agents.
/charly-image:image — image family umbrella (candy: image entries — those carrying base:/from: — in charly.yml, 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).