Fetching from the wire…
Public story · 2026-08-26 · high
SkillForge says agents that save skills for reuse never check if those skills still work, and proposes verifying them before they pile up.
Why now: SkillForge posted to arXiv on August 26, 2026, adding a second critique of skill-bank staleness within weeks.
Agents rarely check whether their saved skills still work, SkillForge argues. This matters for agents meant to run long enough to build up a skill bank. Skills that used to work start blending in with ones that don't, and nothing flags the difference.
The paper points to SkillRL, an existing method for extracting skills during reinforcement learning. Its skill bank only grows because nothing verifies a stored skill against the current environment.
SkillForge's fix has three pieces. It makes skill usage explicit during interaction. That lets the training process optimize both the actions an agent takes and its decisions about which skill to invoke. It adds evidence-based verification, checking whether a skill still holds up. It also draws on multiple pathways to induce skills, rather than one fixed extraction method. Tested against SkillRL on ALFWorld, WebShop, and AppWorld, SkillForge wins consistently across all three.
This is the second paper in as many weeks calling out silent skill staleness in agent systems. One paper flagging the issue is a data point. Two papers raising it within weeks of each other reads like the field starting to treat skill-bank hygiene as a requirement, not a nice-to-have.
The open question is whether agent frameworks start shipping skill verification as a built-in step. The alternative is that builders only notice when an agent pulls from a bank of dead skills, with no error explaining why.
Each link below shares sources, entities, or timing with this story.
SkillPyramid extends Voyager-style libraries with a hierarchical topology plus a self-evolution loop, raising average reward 38% and cutting execution steps 27.7% across ALFWorld, WebShop, and ScienceWorld. The takeaway: don't append every successful trajectory as a new flat s...
It treats the executable runtime, context construction, tool mediation, action validation, execution recovery, as the thing to learn. A separate harness engineer converts batches of target-agent failures into validated executable patches, with same-batch reruns of the frozen t...
Policy-Aware Training Scaffolding converts rollout groups from the latest policy into evidence cards and adjusts agent context per task, removing guidance as the agent improves. The scaffold is discarded at deployment — the skills exist to shape training, not to ship. 18.6% ov...
COTA replaces the expensive expert solver used for runtime intervention with a model that only judges whether a sampled alternative leads to a better continuation than the actor's proposal, returning preferred alternatives as non-binding advice so the original actor replans. T...
LLM as post-hoc critic for step-level Q-values. +7.7% WebShop, +13.8% ALFWorld over GRPO. Third paper in the online RL-for-agents cluster this week. arXiv:2603.08754
Instead of cloning full teacher demonstrations that mismatch the contexts a student hits at test time, spend a fixed teacher-labeling budget on short continuation rollouts that branch from the student's own trajectories (arXiv). On HotpotQA, ALFWorld, and Terminal-Bench-Dev, b...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.