Summary
'Subagents vs Agent Skills' compares loading skill packages as instructions into the main context versus launching them as subagents with dedicated context windows. Subagent execution wins when packages have clear I/O contracts and procedural instructions; skill-loading grows brittle as task horizon increases (context accumulation); the cost is coordination tokens.
Why it matters
This is direct evidence for the architecture choice every agent team faces this year (skill libraries a la Claude Skills vs subagent fleets): encapsulate reusable knowledge as subagents with I/O contracts, and expect the trade to shift further toward subagents as horizons lengthen — at the price of orchestration overhead.
Technical details
| Arxiv | 2609.09233 (Thu 10 Sep digest, announced 2026-09-11T00:00Z) |
|---|---|
| Comparison | skills-as-instructions (main context) vs skills-as-subagents (dedicated context) |
| Findings | subagents win with clear I/O contracts + procedural instructions; skill-loading brittle as horizon grows (context accumulation); cost = coordination tokens |
| Code | not stated in abstract |
Tags
agent-architectureskillsmulti-agentcontext-engineering