Runlayer Engineer Rafal Wilinski: Self-Improving Agents via Skill Distribution and Autonomous Distillation
At AI Engineer World's Fair 2026, Runlayer founding engineer Rafal Wilinski argued that as agents tackle longer tasks, initial trajectory errors become costly. He proposed treating "skills" (playbooks) as reusable knowledge units distributed via the Model Context Protocol (MCP) to overcome client support issues. By autonomously distilling skills from successful and failed agent traces, Runlayer achieved a jump from 36% to 100% success rate in a specific internal test.
ImportanceMaterialEvidenceE3 inspectableWrite-upQuick
When agents can execute complex tasks lasting hours, a flawed initial hypothesis can lead them down rabbit holes involving hundreds of tool calls. Rafal Wilinski, founding engineer at Runlayer, argues that traditional improvements in model capability or prompt engineering do not fully address this because they lack company-specific "procedural knowledge." His solution involves building "skills"—playbooks that agents can read when relevant—and using the Model Context Protocol (MCP) as a unified distribution layer for these skills.
Wilinski identifies three main barriers in the current skill ecosystem: excessive developer-centricity making it hard for non-technical staff; the time cost of writing documentation after difficult work; and uneven client support where many LLM applications cannot load local skill files. To solve this, Runlayer uses an MCP server as a central knowledge base. Clients query the remote server for relevant skills instead of installing local copies. This architecture resolves compatibility issues and allows enterprises to dynamically manage access permissions based on roles and policies.
The key innovation lies in how skills are generated. Drawing inspiration from the Voyager Minecraft agent, Runlayer enables agents to accumulate knowledge automatically during real work. The system analyzes successful traces, distilling them into reusable code or instructions via frontier LLMs. Failed traces are also treated as valuable signals, revealing missing guardrails, dependencies, or edge cases. This process is asynchronous and autonomous, eliminating the need for manual documentation.