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)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.