ov-layers/skills/unsloth-studio/SKILL.md
Unsloth Studio fine-tuning web UI on ports 8888/8000 with vLLM inference. Tier 2 environment-owner meta-layer composing llama-cpp + unsloth, owns pixi.toml. Use when working with Unsloth Studio, the fine-tuning web UI, or the unsloth-studio image.
npx skillsauth add overthinkos/overthink-plugins unsloth-studioInstall 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, supervisord |
| Sub-layers | llama-cpp, unsloth |
| Ports | 8888 (Studio UI), 8000 (vLLM API) |
| Volumes | workspace -> ~/workspace |
| Service | unsloth-studio (supervisord) |
| Install files | layer.yml, pixi.toml |
This layer owns the pixi.toml for the fine-tuning environment and composes two Tier 1 layers via layers: [llama-cpp, unsloth]. Build order: pixi environment → llama-cpp (binaries) → unsloth (vLLM wheel + unsloth pip + patch) → supervisord config.
| Variable | Value |
|----------|-------|
| NVIDIA_PYTHON_PROJECT | ~/.pixi |
| LD_LIBRARY_PATH | /usr/lib64:$HOME/llama.cpp |
Plus from sub-layers: LLAMA_CPP_PATH, UNSLOTH_SKIP_LLAMA_CPP_INSTALL, HF_HOME
Fine-tuning focused ML stack: PyTorch (CUDA 13.0), xformers, transformers, accelerate, vLLM runtime deps, HuggingFace (datasets, tokenizers, sentencepiece), fine-tuning (peft, trl, bitsandbytes, liger-kernel), GGUF tools
Runs pixi run start-studio which executes unsloth studio -H 0.0.0.0 -p 8888. The Studio launches its own vLLM API server on port 8000 for inference and synthetic data generation.
/ov-images:unsloth-studio/ov-layers:llama-cpp — Sub-layer: llama.cpp binaries/ov-layers:unsloth — Sub-layer: vLLM + unsloth pip install + patch/ov-layers:supervisord — Process manager dependency/ov-layers:jupyter-ml — Alternative: ML Jupyter with MCP (same Tier 1 sub-layers)/ov-layers:python-ml — Alternative: core ML without UIUse when the user asks about:
/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)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).