Individual skill

dpo-guide

Align language models with human preferences using Direct Preference Optimization — no reward model, no RL loop.

skills/dpo-guide/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Direct Preference Optimization (DPO) trains a language model directly on preference
pairs — (prompt, chosen, rejected) — without training a separate reward model or
running reinforcement learning. The key mathematical insight is that the optimal
policy under a KL-constrained reward objective has a closed form, which lets you
reframe "maximize this implicit reward" as a simple classification loss on the
policy itself: increase the likelihood of the chosen response relative to the
rejected one, scaled by how far the policy has moved from a reference model.

In practice, DPO is dramatically simpler to run than PPO-based RLHF: it's a single
supervised-style training loop with standard hyperparameters, stable gradients,
and no value network, advantage estimation, or KL scheduling. It has become the
default preference-tuning method for most practitioners. Its limits: it's an