OpenSpace clones itself into reusable AI skills, slashing token costs with FIX/DERIVED lineage

The open-source OpenSpace framework just showed something genuinely interesting: an agent that doesn’t just execute tasks, but captures its own successful reasoning patterns as reusable, versioned skills stored in SQLite. We ran the full pipeline—from sparse cloning the HKUDS repository to live execution of a payroll script task—and watched it evolve a skill with explicit lineage metadata. This isn’t just another agent wrapper. It’s a bet that the unit of reuse in AI shouldn’t be a prompt template, but a proven execution trace that can be recalled for similar problems later.

The workflow itself is refreshingly minimal. After setting up a workspace and pointing OpenSpace at Claude Sonnet 4.5, we asked it to write a Python function that parses a CSV of employee hours and computes payroll with overtime at 1.5x beyond 40 hours. The agent didn’t just return code. It executed it on a synthetic example and then, crucially, emitted an evolved skill—a structured record of what worked, complete with an origin tag marking it as FIX, DERIVED, or CAPTURED. That classification system is the secret sauce. FIX skills are hand-authored baselines. DERIVED skills emerge from successful task completions. CAPTURED skills come from observing host-agent interactions.

The database inspection is where things get concrete. Dumping the SQLite tables reveals version chains and parent-child relationships between skills. You can trace exactly which earlier success a new skill was derived from. For teams burning through API credits on repetitive reasoning, this lineage means you’re not starting from scratch every time. The system can warm-start a task by retrieving a previously validated approach, verify it still applies, and only invoke the expensive model when adaptation is actually needed.

I’m cautiously optimistic about the MCP server integration. OpenSpace exposes skills over a streamable HTTP endpoint, which means external host agents can query the skill library as a tool. The custom SKILL.md we created got picked up immediately. The real test, though, is whether this lineage graph stays coherent after a few hundred tasks. Skill drift is the silent killer of these systems—a derived skill that was optimal last week might be subtly wrong today, and version numbers alone don’t tell you when that happened. Still, the architecture is sound, and for the price of a SQLite database, it’s a low-risk experiment worth running.