OpenSpace Review: A Skill Management Layer for AI Agents

Key highlights:

• From HKUDS (the University of Hong Kong Data Intelligence Lab, the group behind LightRAG and several trending agent repos), MIT-licensed, Python 3.12+

• v2 shipped July 2026 — added a quality layer, controlled evolution, and a package-based cloud "Skill Wiki"

• Plugs in over MCP: works with Claude Code, Codex, Cursor, OpenClaw, nanobot, or any MCP-capable host

• Benchmark: on the same frozen backbone, a "cold" run scored 65.2% and warmed up to 78.7% as the trusted skill library evolved — with a reported ~46% reduction in token usage

• Three evolution modes — FIX, DERIVED, CAPTURED — decide when and how a skill changes, all with version history

Everyone building with agents in 2026 hit the same wall: skills scale badly. The "skills" pattern — a folder of SKILL.md files that teach an agent reusable procedures — was popularized by Anthropic and is now everywhere, from Claude Code to OpenClaw. It works great with ten skills. It falls apart at a few hundred.

OpenSpace is HKUDS's answer to that scaling problem. Its own framing is blunt: when an agent performs poorly, the problem is not always the model. Sometimes the agent simply fails to retrieve the right skill, apply it to the right task, or choose the version that actually works. As your library grows, more choices make the right skill harder to find, not easier.

So OpenSpace reframes skills as something to be managed across a full lifecycle:

Most "agent memory" systems accumulate. You run a task, something gets saved, the pile grows. OpenSpace's central bet is that accumulation without a quality signal is noise. Its v2 architecture has four connected layers, and quality is the thread running through all of them.

This layer answers one question: which skills can the agent actually trust? Rather than trusting a skill's description, OpenSpace records what happened on real runs:

- Skill outcomes — was a skill selected, applied, did it complete the task, or did the agent fall back to something else?

There's a local dashboard (Node.js ≥ 20) that visualizes how your skills evolve — browse skills, track lineage, and compare diffs across versions:

For a team, this is where the "shared knowledge" story becomes tangible: you can see which skills a colleague's agent captured, review the lineage, and decide whether to import them.

This is a condensed version. The full article includes architecture diagrams, code examples, comparison tables, and practical use cases.

👉 Read the complete analysis on andrew.ooo

Topics: ai agent, skills, openspace, hkuds, mcp