This is the router skill for the fine-tuning lifecycle: it decides whether fine-tuning is the right tool at all, and if so, which method and which base-model size class. Every other skill in this plugin assumes this routing already happened — start here before opening lora-qlora. Use it to give an agent explicit responsibilities, steps and constraints.

The full procedure behind SKILL.md's "Judge Calibration Is a Prerequisite" section. Any grader routed to an LLM-judge follows this before its verdicts count toward a pass rate or a checkpoint promotion decision. Use it to give an agent explicit responsibilities, steps and constraints.

Runnable examples for the four grader shapes named in SKILL.md's Graders section: schema-compliance, exact-match with normalization, execution-based, and LLM-judge. Every grader returns a binary pass/fail — never a Likert score — per the plugin-wide rule. Wire each one to exact. Use it to give an agent explicit responsibilities, steps and constraints.

The Phase 0 gate for the whole plugin: finetuning-method-selection and every downstream skill assume this harness exists before a training config gets written. The harness is not a run-end side artifact — it is the data-curation engine. The same labeled traces that build the go. Use it to give an agent explicit responsibilities, steps and constraints.

Full detail backing SKILL.md's Synthetic Data Rules section: the generation-method ranking, the filter funnel candidate generations pass through before joining the training set, and the teacher→student distillation pattern. Base models are never named as recommendations here. Use it to give an agent explicit responsibilities, steps and constraints.

Concrete JSONL examples for every format in SKILL.md's Format Selection table, a template-application code sketch using current TRL conventions, and the ShareGPT→role/content conversion note. Base models are never named here — every code example uses a BASE MODEL placeholder;. Use it to give an agent explicit responsibilities, steps and constraints.

This skill assumes finetuning-method-selection already routed here — the next step is preparing data, not choosing a method. What follows: format selection by target method, the template/packing mechanics behind the most common silent training failures, rules for mixing in synt. Use it to give an agent explicit responsibilities, steps and constraints.

Complete promotion-report.md template, the drift-suite scoring table, the paired-arena protocol, and a replay-mix configuration example referenced from SKILL.md. BASE MODEL and CHECKPOINT are placeholders throughout — no base model family names appear in this file. Benchm. Use it to give an agent explicit responsibilities, steps and constraints.

The Phase 5 gate for the whole plugin: a checkpoint that trains cleanly and beats its task metric still doesn't ship without clearing all four stages below. eval-harness-first built the suite re-run here — this skill is where that suite's baseline decides something. Use it to give an agent explicit responsibilities, steps and constraints.

This command orchestrates the eval-gated fine-tuning lifecycle across seven phases, each owned by a specialist agent and gated by the artifact the prior phase produced:. Use it to give an agent explicit responsibilities, steps and constraints.

You are the fine-tuning training engineer: the workhorse who takes a training-brief.md someone else already justified and turns it into a dataset, a running job, and an exported artifact. You don't re- litigate method or model choice, and you don't decide whether a checkpoint s. Use it to give an agent explicit responsibilities, steps and constraints.

You are the fine-tuning eval engineer: the independent gatekeeper who builds the measuring stick before anyone trains against it, and reads that same measuring stick to decide whether a trained checkpoint ships. You own the two phases that bound the lifecycle — Phase 0 before a t. Use it to give an agent explicit responsibilities, steps and constraints.

You are the fine-tuning architect: a skeptical strategist who decides whether fine-tuning is the right tool at all before anyone opens a training config. You are the gate-keeper standing between "the user wants to fine-tune" and the first line of a training script — most requests. Use it to give an agent explicit responsibilities, steps and constraints.

vector-index-tuning — templates and worked examples captures reusable agent playbook guidance for agent design & orchestration. Use it to give an agent explicit responsibilities, steps and constraints.

similarity-search-patterns — templates and worked examples captures reusable agent playbook guidance for agent design & orchestration. Use it to give an agent explicit responsibilities, steps and constraints.

rag-implementation — detailed patterns and worked examples captures reusable agent playbook guidance for agent design & orchestration. Use it to give an agent explicit responsibilities, steps and constraints.

1. Keep It DRY : Use templates to avoid repetition 2. Validate Early : Check variables before rendering 3. Version Templates : Track changes like code 4. Test Variations : Ensure templates work with diverse inputs 5. Document Variables : Clearly specify required/op. Use it to give an agent explicit responsibilities, steps and constraints.

1. Establish Baseline : Always measure initial performance 2. Change One Thing : Isolate variables for clear attribution 3. Test Thoroughly : Use diverse, representative test cases 4. Track Metrics : Log all experiments and results 5. Validate Significance : Use st. Use it to give an agent explicit responsibilities, steps and constraints.

Few-shot learning enables LLMs to perform tasks by providing a small number of examples (typically 1-10) within the prompt. This technique is highly effective for tasks requiring specific formats, styles, or domain knowledge. Use it to give an agent explicit responsibilities, steps and constraints.

prompt-engineering-patterns — detailed patterns and worked examples captures reusable agent playbook guidance for agent design & orchestration. Use it to give an agent explicit responsibilities, steps and constraints.