Skill Wiki v0.1.0

Docs

On this page

Documentation

Skill Wiki documentation

Skill Wiki turns a skill from one bulky SKILL.md blob into a typed wiki of atoms — each atom addressable, linked into a declared edge graph, and retrieved on demand.

The mental model

Typed atoms

Every piece of knowledge is one atom — and an atom always declares what kind it is: a rule, a pattern, a value, a fact, a tradeoff, and so on. The spec defines 28 kinds. Kinds aren't decoration; they tell the runtime what fields to expect, how to render the atom at each projection level, and which retrieval strategies make sense. Free prose has no kind, and that is why SKILL.md can't be queried — Skill Wiki replaces prose with types.

A declared edge graph

Atoms link to other atoms through 14 typed verbsrequires, contradicts, refines, validates-with, and the rest. The graph is declared in the atom files, compiled into _index.xml, and traversable at query time. An agent doesn't search a flat document; it walks a graph from a seed atom outward, pruning by verb and by intent.

Lazy projection

A skill ships up-front as a ~3 KB index — the names, kinds, and edges of every atom, no bodies. When the agent's brief actually calls for an atom, the runtime streams in one of three projections: summary (~30 tokens), core (~150), or full (~380). The agent pays for what it reads, not for what the corpus contains.

Why this exists

The default way to give an agent a skill is to dump a SKILL.md into context. It works for a thousand tokens; it falls apart at ten thousand. The blob can't be queried, can't declare its own structure, and blows past the budget long before the agent has read anything that matters. Skill Wiki is an answer: keep skills as wikis of typed, linked atoms, ship only the index, and let the runtime fetch what the task needs.

Conventions

  • Prime — the underlying protocol. A Prime is a self-contained @scope of typed atoms — what gets published and installed.
  • Atom — one typed unit of knowledge. Has a kind, a domain, an id, projection levels, and edges.
  • Edge — a typed relationship between two atoms. 14 verbs in v1.
  • Projection — one of three rendered Markdown views: summary (~30 tok), core (~150 tok), full (~380 tok).
  • Index — the _index.xml file an agent loads at boot. Lists every atom; ~3 KB; never contains atom bodies.