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)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).