What problem does it solve?
Teams often jump straight into fine-tuning when RAG or prompt engineering would solve the problem more cheaply, or pick the wrong training method for the data they actually have. This Skill acts as the router for the entire fine-tuning lifecycle: it decides whether to fine-tune at all, and if so, which method (SFT, DPO/ORPO/KTO, GRPO/RLVR, or continued pretraining) and which base-model size class fit the task and hardware.
Core Features & Use Cases
- Off-Ramp Checks First: Routes volatile-fact problems to RAG and unstable-behavior problems to prompt engineering before any training run is considered.
- Data-Shape Method Router: Maps the data you have (demonstrations, preference pairs, unpaired thumbs up/down, verifiable pass/fail signals) to the correct method, with worked routing examples and common mistakes.
- Memory Feasibility Worksheets: Estimates weights, optimizer states, gradients, and activations per method and dtype, with anchors like 8B-class LoRA at ~16GB and 70B-class QLoRA at ~40GB.
- Use Case: You have unpaired reviewer thumbs-up/down feedback on model responses. The router identifies this as an unpaired preference signal and routes you to KTO rather than DPO, then hands off to the preference-optimization skill.
Quick Start
Ask the assistant to decide whether your task needs fine-tuning, RAG, or prompt engineering, and which training method and model size class to use.