ov-foundation/skills/python-ml-layer/SKILL.md
Core ML/AI Python environment with PyTorch, vLLM runtime deps, and CUDA support. Tier 2 environment-owner meta-layer that composes llama-cpp. Use when working with machine learning, PyTorch, HuggingFace, or GPU computing.
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.
| Property | Value |
|----------|-------|
| Dependencies | cuda |
| Sub-layers | llama-cpp |
| Install files | layer.yml, pixi.toml, tasks: |
This layer owns the pixi.toml for the core ML Python environment and composes the llama-cpp Tier 1 layer via layers: [llama-cpp]. Build order: pixi environment → llama-cpp (binaries) → python-ml user-phase tasks (vLLM wheel).
| Variable | Value |
|----------|-------|
| NVIDIA_PYTHON_PROJECT | ~/.pixi |
| LD_LIBRARY_PATH | /usr/lib64:$HOME/llama.cpp |
Plus from llama-cpp sub-layer:
| Variable | Value |
|----------|-------|
| LLAMA_CPP_PATH | ~/llama.cpp |
| PATH (appended) | ~/llama.cpp |
PyPI: PyTorch >= 2.10.0 (CUDA 13.0), xformers, transformers, accelerate, safetensors, numpy, scipy, einops, pillow, kornia, spandrel, torchsde, vLLM runtime deps (blake3, flashinfer, numba, ray, xgrammar, etc.), gguf, pydantic, aiohttp
pip install --no-deps)/ov-foundation:python-ml/ov-immich:immich-ml/ov-jupyter:llama-cpp — Sub-layer: llama.cpp binaries (composed via layers:)/ov-foundation:cuda — CUDA toolkit dependency/ov-jupyter:jupyter-ml — Full ML + Jupyter variant (superset of python-ml's pixi env)/ov-jupyter:unsloth-studio — Fine-tuning variant (similar pixi env + unsloth)Use when the user asks about:
python-ml layer, its packages, or its meta-layer composition/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval 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).