WikiSkill: Compiling Agent Experience into Persistent Knowledge
This post introduces WikiSkill, a paradigm proposed by a joint Google Research / Google DeepMind team in the paper *"WikiSkill: Compiling Agent Experience into Persistent Knowledge for Skill Evolution"* (arXiv:2608.27454, listed as published August 27, 2026).
Key points
- The problem: Self-evolving agents (e.g., Reflexion, Voyager) that distill trial-and-error history directly into prompt rules suffer from context bloat, conflicting rules, and—critically—loss of hard-won failure lessons whenever a skill update must be rolled back.
- The idea: WikiSkill acts as a "cognitive compiler," decoupling agent memory into three layers instead of stuffing experience into the prompt.
- If scores improve → the new skill is adopted.
- If scores drop → the Skill layer rolls back to the previous stable version, but the Wiki layer records a failure post-mortem that is retained forever.
- Daily self-iteration without repeated full-parameter fine-tuning.
- Human-agent knowledge symbiosis: the Wiki layer uses human-readable Markdown with hyperlinks, so human experts can audit, correct, or manually author entries.
- "Knowledge compound interest": every failure becomes a permanent, transferable knowledge asset.
- Paper: *WikiSkill: Compiling Agent Experience into Persistent Knowledge for Skill Evolution*
- Authors: Liyan Tang, Cyrus Rashtchian, Chun-Sung Ferng, Andrew Tomkins, Da-Cheng Juan, Tu Vu
- Affiliations: Google Research / Google DeepMind / Virginia Tech
- Preprint: arXiv:2608.27454
The three-layer workspace
1. Raw Layer — An immutable, append-only ledger of every atomic interaction: tool calls, API errors, chain-of-thought, observations. Provides auditable ground truth. 2. Wiki Layer — A monotonically growing, structured encyclopedia: Pattern pages (root causes of specific errors), Strategy pages (task decomposition), implicit tool-usage rules. Knowledge is never deleted, even if a downstream skill update fails. 3. Skill Layer — A highly compressed set of executable rules/checklists (e.g., a handful of "golden rules") injected into the reasoning context with minimal token cost.
Asymmetric gating and rollback
When a Skill Proposer generates a new skill, it is validated on an independent validation set:
The post compares this to human civilization: policies may be repealed, but books preserve the lessons. The next skill proposal reads the failure archive and avoids repeating mistakes.
Counterintuitive finding
A control experiment found that agents fed the full wiki content via RAG during reasoning performed worse than agents reading only the compiled, concise skills. Interpretation: declarative knowledge is for background curation and reflection; procedural knowledge is for fast, decisive execution. Direct wiki retrieval causes context overload and "analysis paralysis."
Reported benchmark results
| Dimension | Zero-shot baseline | Reflexion/Voyager | WikiSkill | | :--- | :---: | :---: | :---: | | Task success gain | baseline | +12–18% | +35–52% | | Rule conflicts / overfitting | — | High, grows with rounds | Near zero (gated) | | Context token usage | Very low | Exponential bloat | Constant, low | | Small-model capability | Weaker than large models | Still behind | Evolved small models surpass large models |
The post claims that lightweight models (e.g., Gemini Flash-class, Qwen-7B/14B) evolved via WikiSkill surpassed much larger unevolved base models on long-horizon benchmarks (OSWorld, WebArena, SWE-bench, AgentBench/ToolQA).