ov-jupyter/skills/unsloth/SKILL.md
Unsloth LLM fine-tuning library with vLLM integration. Tier 1 post-install layer — no pixi.toml, requires pixi env from a parent layer (python-ml, jupyter-ml, unsloth-studio). Use when working with Unsloth, LLM fine-tuning, or vLLM wheel installation.
npx skillsauth add overthinkos/overthink-plugins unslothInstall 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 | None (requires pixi env from parent) |
| Volumes | models -> ~/.cache/huggingface |
| Aliases | unsloth -> unsloth |
| Install files | layer.yml, tasks: |
This layer has no pixi.toml and no depends. It installs pip packages into the pixi environment established by a Tier 2 "environment-owner" parent layer. The user-phase tasks run AFTER the parent's pixi COPY in the final image build.
Cannot be used standalone — must be composed into an environment-owner layer via the layers: field.
| Variable | Value |
|----------|-------|
| UNSLOTH_SKIP_LLAMA_CPP_INSTALL | 1 |
| HF_HOME | ~/.cache/huggingface |
pip install --no-deps) — installed here because vLLM wheel must run after pixi env existspip install --no-deps) — incompatible with transformers 5.x in pixi solvepip install) — pixi resolver conflict prevents solving these via conda-forgepatch_vllm_size_nodes.py) — fixes _decompose_size_nodes bug where getitem users and x.size(dim) patterns crash during model compilation (upstream: vllm-project/vllm#38360)layers: field)/ov-jupyter:jupyter-ml — layers: [llama-cpp, unsloth, jupyter-mcp]/ov-jupyter:unsloth-studio — layers: [llama-cpp, unsloth]/ov-jupyter:llama-cpp — llama.cpp binaries (often paired as sibling Tier 1 layer)/ov-jupyter:unsloth-studio — Studio web UI (Tier 2 parent, owns pixi.toml)/ov-jupyter:jupyter-ml — ML Jupyter with MCP (Tier 2 parent, owns pixi.toml)/ov-foundation:python-ml — Core ML environment (Tier 2, uses vllm pip install in its own tasks: instead)/ov-jupyter:jupyter-ml (via jupyter-ml metalayer)/ov-jupyter:jupyter-ml-notebook (via jupyter-ml metalayer)/ov-jupyter:unsloth-studio (via unsloth-studio metalayer)Use when the user asks about:
unsloth host alias/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.