ov-images/skills/unsloth-studio/SKILL.md
Unsloth Studio fine-tuning web UI with CUDA GPU support, vLLM inference, and llama.cpp. Runs as a supervisord service on ports 8888 (Studio) and 8000 (vLLM API). MUST be invoked before building, deploying, configuring, or troubleshooting 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.
Unsloth Studio web UI for LLM fine-tuning with GPU acceleration.
| Property | Value | |----------|-------| | Base | nvidia | | Layers | agent-forwarding, unsloth-studio, notebook-finetuning, dbus, ov | | Platforms | linux/amd64 | | Ports | 8888, 8000 | | Registry | ghcr.io/overthinkos |
The unsloth-studio layer is a Tier 2 environment-owner meta-layer that:
layers: [llama-cpp, unsloth]Build order: pixi environment → llama-cpp (binaries) → unsloth (vLLM 0.19 wheel + unsloth pip + torch.compile patch) → supervisord config
fedora → nvidia (CUDA base)pixi → python → supervisord (transitive)unsloth-studio — Tier 2 meta-layer (owns pixi.toml, service config)llama-cpp — llama.cpp binaries (Tier 1, via layers:)unsloth — vLLM 0.19 + unsloth pip install + torch.compile patch (Tier 1, via layers:)| Port | Service | Protocol | |------|---------|----------| | 8888 | Unsloth Studio UI | HTTP | | 8000 | vLLM API server | HTTP |
| Name | Path | Purpose | |------|------|---------| | models | ~/.cache/huggingface | HuggingFace model cache | | workspace | ~/workspace | Training data and outputs |
ov image build unsloth-studio
ov config unsloth-studio
ov start unsloth-studio
# Open http://localhost:8888
/ov-layers:unsloth-studio — Studio web UI service + pixi.toml (Tier 2)/ov-layers:llama-cpp — llama.cpp binaries (Tier 1 sub-layer)/ov-layers:unsloth — vLLM 0.19 + unsloth fine-tuning + torch.compile patch (Tier 1 sub-layer)/ov-layers:notebook-finetuning — 37 Unsloth fine-tuning notebooks provisioned into workspace volume/ov-layers:nvidia — GPU runtime and CDI device auto-detection (base)/ov-layers:cuda — CUDA toolkit and libraries (via nvidia base)/ov-layers:dbus — session bus for desktop notifications/ov-layers:ov — in-container ov binary (enables ov test dbus notify)/ov-layers:agent-forwarding — SSH/GPG/direnv agent forwarding/ov-images:nvidia — parent (GPU without Studio)/ov-images:jupyter-ml — alternative ML UI with JupyterLab + CRDT MCP (same Tier 1 sub-layers)/ov-images:python-ml — ML libraries without any UI/ov-images:jupyter — legacy Jupyter with ML (shares port 8888)After ov start:
ov status unsloth-studio — container runningov service status unsloth-studio — all services RUNNINGcurl -s -o /dev/null -w '%{http_code}' http://localhost:8888 — Studio HTTP returns 200MUST be invoked when the task involves the unsloth-studio image, LLM fine-tuning via web UI, or Unsloth Studio deployment. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)/ov:build — build.yml vocabulary (distros, builders, init-systems)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.