A working unit — code, a skill, a hard-won pattern — packaged once, versioned, and dropped into any project with a single call. This is the part a memory tool doesn't have.
A memory tool can tell an agent what it once knew. But knowing isn't the same as having. When you've solved something once — a notification hook, a review template, an integration pattern — you shouldn't paste it by hand into the next project. You should install it. That's the difference between remembering and building.
Turn a proven note or piece of code into a versioned module. It carries its own name, category, and tags.
An agent installs the module with one call. No copy-paste, no re-deriving. The knowledge arrives intact.
These aren't mockups — they're modules running in a live workspace today. Built once, installable anywhere.
WhatsApp notification system — send messages via webhook.
A reusable lessons-learned template — distilled from real quality-system work.
The first module ever published to Retia — the registry proving itself.
The Model Context Protocol is bringing Skills to the protocol level. When it lands, Retia will close the loop: define a module once, and have it export as an Anthropic Skill — so the same unit of knowledge becomes both code your agents install and runtime guidance they follow.
Define once. Both the code and the guidance flow from the same source. We're building this toward the July MCP spec — it's a direction we're committed to, not a promise we're hiding behind.