This skill assumes finetuning-method-selection already routed here: the data shape is image+text demonstrations, not preference pairs or a verifiable reward signal, and the base is a vision-language model rather than a text-only one. lora-qlora-recipes covers the text-only Lo. Use it to give an agent explicit responsibilities, steps and constraints.
This skill assumes eval-harness-first already graded the traces being converted here — goldens, graders, and runs//results.json all exist before conversion starts. This is the flywheel edge that skill names in its own flow: "the same labeled traces become the training set." C. Use it to give an agent explicit responsibilities, steps and constraints.
This skill assumes finetuning-method-selection already routed here because the data shape is preference pairs or unpaired thumbs-up/down feedback, not demonstrations (that's lora-qlora-recipes) or a verifiable reward signal (that's grpo-rlvr-training). What follows is metho. Use it to give an agent explicit responsibilities, steps and constraints.
This skill assumes finetuning-method-selection already routed here because the target behavior has a verifiable pass/fail signal — not demonstrations (lora-qlora-recipes) or preference pairs (preference-optimization). What follows is when RL is the right tool, the reference. Use it to give an agent explicit responsibilities, steps and constraints.
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.
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.
This skill assumes finetuning-method-selection already routed here: the data shape is image+text demonstrations, not preference pairs or a verifiable reward signal, and the base is a vision-language model rather than a text-only one. lora-qlora-recipes covers the text-only Lo. Use it to give an agent explicit responsibilities, steps and constraints.
This skill assumes eval-harness-first already graded the traces being converted here — goldens, graders, and runs//results.json all exist before conversion starts. This is the flywheel edge that skill names in its own flow: "the same labeled traces become the training set." C. Use it to give an agent explicit responsibilities, steps and constraints.
This skill assumes finetuning-method-selection already routed here because the data shape is preference pairs or unpaired thumbs-up/down feedback, not demonstrations (that's lora-qlora-recipes) or a verifiable reward signal (that's grpo-rlvr-training). What follows is metho. Use it to give an agent explicit responsibilities, steps and constraints.
This skill assumes finetuning-method-selection already routed here because the target behavior has a verifiable pass/fail signal — not demonstrations (lora-qlora-recipes) or preference pairs (preference-optimization). What follows is when RL is the right tool, the reference. Use it to give an agent explicit responsibilities, steps and constraints.
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.
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.