ov-foundation/skills/python-ml/SKILL.md
GPU-accelerated Python ML environment with CUDA, PyTorch, and llama.cpp. No Jupyter server — use as a base for ML workloads or interactive shell. MUST be invoked before building, deploying, configuring, or troubleshooting the python-ml image.
npx skillsauth add overthinkos/overthink-plugins python-mlInstall 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 Python environment with ML libraries — PyTorch, transformers, vLLM, llama.cpp.
| Property | Value | |----------|-------| | Base | nvidia | | Layers | agent-forwarding, python-ml | | Platforms | linux/amd64 | | Registry | ghcr.io/overthinkos |
The python-ml layer is a Tier 2 environment-owner meta-layer that:
llama-cpp (Tier 1 sub-layer) via layers: [llama-cpp]Build order: pixi environment → llama-cpp (binaries) → vLLM 0.19 wheel
fedora → nvidia (CUDA base)pixi → python (transitive)python-ml — ML pixi environment (Tier 2, owns pixi.toml)llama-cpp — llama.cpp binaries (Tier 1, via layers: field)ov image build python-ml
ov shell python-ml
# python -c "import torch; print(torch.cuda.is_available())"
/ov-foundation:python-ml — ML Python packages via pixi (Tier 2 meta-layer)/ov-jupyter:llama-cpp — llama.cpp binaries (sub-layer)/ov-foundation:cuda — GPU support (via nvidia base)/ov-foundation:nvidia — parent (GPU without ML packages)/ov-jupyter:jupyter-ml — adds JupyterLab + collaboration + MCP + unsloth on top of ML stack/ov-jupyter:jupyter — legacy Jupyter with ML stack (monolithic)/ov-jupyter:unsloth-studio — fine-tuning UI with similar ML stackAfter ov image build:
ov shell python-ml -c "python -c 'import torch; print(torch.cuda.is_available())'" — CUDA OKov shell python-ml -c "python -c 'import vllm; print(vllm.__version__)'" — vLLM OKov shell python-ml -c "ls ~/llama.cpp/llama-quantize" — llama.cpp OKMUST be invoked when the task involves the python-ml image, ML training environments, or GPU-accelerated Python. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov-build: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).