ov-layers/skills/notebook-finetuning/SKILL.md
Unsloth fine-tuning notebook collection provisioned into the workspace volume at deploy time. Data-only layer — no packages, no services, no dependencies. Use when working with notebook-finetuning, Unsloth training notebooks, or unsloth-studio data provisioning.
npx skillsauth add overthinkos/overthink-plugins notebook-finetuningInstall 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) |
| Packages | (none) |
| Services | (none) |
| Volumes | workspace -> ~/workspace (from unsloth-studio) |
| Data | data/finetuning -> workspace volume, dest: finetuning |
| Install files | (none) |
This is a data layer — it uses the data: field in layer.yml to map a directory of notebooks to a named volume with a subdirectory destination:
info: "Unsloth fine-tuning notebook collection for unsloth-studio"
data:
- src: data/finetuning
volume: workspace
dest: finetuning
At build time, the contents of data/finetuning/ are staged into /data/workspace/finetuning/ inside the image.
At deploy time, when the workspace volume is configured as a bind mount (ov config --bind workspace), ov config copies the staged data into the host-backed volume directory at <workspace>/finetuning/. This seeds the volume with ready-to-use training notebooks.
The dest: finetuning field places the notebooks in a subdirectory rather than the volume root, keeping the workspace organized alongside other content.
37 Jupyter notebooks + 1 manifest, organized by training category:
| Category | Notebooks | Models |
|----------|-----------|--------|
| 00-Setup | 00_Unsloth_Setup.ipynb | (general) |
| 01-FastInference | 3 notebooks | Llama, Qwen, Qwen_Think |
| 02-Vision Training | 2 notebooks | Ministral, Pixtral |
| 03-SFT Training | 5 notebooks | Ministral (text + vision), Pixtral, Qwen, Qwen_Think |
| 04-GRPO Training | 5 notebooks | Ministral (text + vision), Pixtral, Qwen, Qwen_Think |
| 05-DPO Training | 2 notebooks | Qwen, Qwen_Think |
| 06-Reward Training | 2 notebooks | Qwen, Qwen_Think |
| 07-RLOO Training | 5 notebooks | Ministral (text + vision), Pixtral, Qwen, Qwen_Think |
| 08-QLoRA | 12 notebooks | Ministral, Qwen_Think (alpha scaling, continual learning, rank comparison, multi-adapter, quantization comparison, target modules) |
Manifest: notebooks.yaml — structured catalog of all notebooks with metadata.
# image.yml
unsloth-studio:
layers:
- unsloth-studio
- notebook-finetuning
# ... other layers
# Deploy with bind-backed workspace volume
ov config unsloth-studio --bind workspace
# Notebooks are seeded at <workspace>/finetuning/ on first config
ov start unsloth-studio
# Open http://localhost:8888 → navigate to finetuning/
The notebooks include several workarounds for upstream library changes:
packing=True in SFTConfig (19 notebooks) -- Required for TRL 1.0 compatibility. Without it, SFT training fails with the updated TRL APIos.environ["UNSLOTH_ENABLE_FLEX_ATTENTION"] = "0" (16 Ministral/Pixtral notebooks) -- Disables flex_attention to work around a transformers 5.5 bug that crashes these model architecturesmax_memory={0: "14GB"} in model loading (3 Pixtral-12B notebooks) -- Fixes accelerate device_map estimation for Pixtral-12B models that would otherwise OOMmax_prompt_length removed from DPOConfig (2 DPO notebooks) -- Parameter deprecated and removed in TRL 1.0/ov-images:unsloth-studio/ov-images:jupyter-ml-notebook/ov:layer -- data field documentation and layer authoring rules/ov:config -- data provisioning during ov config setup/ov:deploy -- volume backing configuration (bind, named, encrypted)/ov-layers:unsloth-studio -- the Tier 2 meta-layer that owns the workspace volume/ov-layers:notebook-templates -- sibling data layer pattern (starter notebooks for jupyter)/ov-images:unsloth-studio -- the image that includes this layerUse when the user asks about:
data: field with dest: subdirectory mapping/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).