Before the Next Rollout: Diagnosing Skill Utility Shifts from Policy Updates
Organizations: Fudan University · Pyra
Abstract
Skill-evolution methods typically analyze execution trajectories to guide agent skill refinement. However, policy updates can change the behavioral effects and marginal utility of an unchanged skill. Attribution based on earlier trajectories may therefore no longer reflect the skill's contribution under the updated policy. Moreover, trajectory failures can arise from multiple factors, making individual skill contributions difficult to isolate. We evaluate whether policy-update signals contain predictive information about changes in skill marginal utility. At fixed contexts from pre-update training rollouts, we measure how policy updates change the contrast in token preferences between skill and control conditions. Combining these interaction shifts with advantage estimates yields reward-directed readouts for diagnosing utility changes. The readouts reuse existing training rollouts and require only forward passes for single-step action scoring, without additional post-update rollout evaluation. Our experiments show that policy updates can alter skill marginal utility and that policy-update readouts carry diagnostic information for identifying skills with declining utility. Integrating readout-guided prioritization into skill evolution improves downstream performance while reducing policy and editor token consumption.
Figures & tables
| Benchmark | Skills | Decline | Readout | Decline diagnosis | Magnitude | |||
| AP | P@5 | |||||||
| ALFWorld | 25/44 | 32.0% | Magnitude | 0.483 | 0.643 | 0.200 | 0.170 | |
| Reward | 0.567 | 0.833 | 0.416 | 0.400 | ||||
| WebShop | 42/54 | 50.0% | Magnitude | 0.739 | 0.600 | 0.334 | 0.400 | 0.505 |
| Reward | 0.853 | 0.800 | 0.778 | 0.800 | 0.073 | |||
| HotpotQA | 22/30 | 36.4% | Magnitude | 0.560 | 0.542 | 0.080 | 0.400 | 0.390 |
| Method | ALFWorld | WebShop | HotpotQA | NQ | Spreadsheet Bench | LogicBench | |
|---|---|---|---|---|---|---|---|
| Seen SR | Unseen SR | Score | EM | EM | Acc. | Acc. | |
| GRPO (no skills) | 65.36 3.7 | 64.55 4.3 | 55.10 2.6 | 50.10 1.6 | 47.60 1.1 | 18.50 2.6 | 81.90 1.5 |
| GRPO (fixed skills) | 68.21 3.1 | 67.16 3.0 | 58.49 2.5 | 51.30 2.2 | 49.30 1.8 | 22.50 2.3 | 83.37 1.7 |
| SkillRL | 75.36 3.3 | 74.63 3.5 | 59.32 2.2 | 52.40 1.2 | 51.70 0.7 | 27.00 2.4 | 86.20 1.3 |
| WikiSkill | 69.64 2.8 | 68.28 3.7 | 58.84 1.8 | 51.90 1.7 | 50.40 0.8 | 26.60 2.1 | 85.30 1.2 |
| EvoSkill | 67.86 3.6 | 66.04 4.3 | 58.72 2.4 | 51.20 1.1 | 49.80 1.2 | 24.70 2.8 | 84.50 1.8 |
| Benchmark | Method | Inference | Revision | ||||
|---|---|---|---|---|---|---|---|
| Steps | Policy in. (k) | Policy out. (k) | Editor in. (M) | Editor out. (M) | Accepted/ Proposed | ||
| ALFWorld | Full-failure | 24.76 | 30.46 | 3.07 | 14.940 | 0.098 | 22/30 |
| Ours | 18.31 | 16.48 | 4.76 | 3.475 | 0.092 | 25/29 | |
| WebShop | Full-failure | 10.74 | 14.81 | 0.19 | 1.868 | 0.026 | 18/30 |
| Ours | 6.88 | 10.21 | 0.17 | 1.389 | 0.046 | 19/26 | |
| HotpotQA | Full-failure | 3.45 | 7.25 | 1.12 | 6.200 | 0.084 | 21/30 |
| Selector | ALFWorld | WebShop | |
|---|---|---|---|
| Seen SR | Unseen SR | Score | |
| Random top-5 | |||
| Failure-frequency | |||
| Magnitude-only | |||
| Reward-directed | |||
Appendix figures & tables5 assets
Supplementary material from the paper’s appendix.
Appendix
| Benchmark | Interaction | Train | Eval |
|---|---|---|---|
| ALFWorld | Multi-Step | 3,553 | 140 / 134 |
| WebShop | Multi-Step | 10,587 | 500 |
| HotpotQA | Multi-Step | 90,447 | 7,405 |
| SpreadsheetBench | Multi-Step | 600 | 212 |
| NQ | Multi-Step | 79,168 | 3,610 |
| LogicBench | Single-Step | 11,524 | 760 |
| Benchmark | Source | Skills |
|---|---|---|
| ALFWorld | SkillRL | 44 |
| WebShop | SkillRL | 54 |
| HotpotQA | SkillRL (Search) | 30 |
| NQ | SkillRL (Search) | 30 |
| SpreadsheetBench | Trajectory distillation | 32 |
| LogicBench | SRA-Bench | 19 |
| Setting | Default value |
|---|---|
| Model size | Qwen3.5-4B (4B parameters) |
| Compute hardware | 8 NVIDIA B200 GPUs |
| Training time | 24 hours per run |
| Compute budget | 192 GPU-hours per run |
| Optimizer | AdamW, full-parameter training |
| Learning-rate schedule | Constant, no warmup |