Back to corpus
architecturetechnical paper candidatescore 54
Skill Entity Migration Guide
How to convert legacy `SKILL.md` files into SEA skill entities with typed inputs/outputs, scoring hooks, and hot-reload support.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
How to convert legacy `SKILL.md` files into SEA skill entities with typed inputs/outputs, scoring hooks, and hot-reload support.
The Skill Entity Architecture (SEA) transforms static SKILL.md files into autonomous daemon entities with:
- **Typed inputs/outputs** — structured scoring via Tier 1 (embedding) and Tier 2 (MiniMax LLM) - **Persistent memory** — activation history, hot/cold topic evolution, mute state - **Versioning** — SHA-256 content hashing, semantic versions, rollback snapshots - **Hot-reload** — edit SKILL.md, watcher detects changes, caches update without restart
This guide walks through migrating any skill from the legacy format to a fully operational SEA entity.
| Service | Location | Required For | |---------|----------|-------------| | Ollama (all-minilm) | `http://[ip]:11434` (Mac4) | Tier 1 embedding generation | | MiniMax-M2.5 | `http://localhost:18080` | Tier 2 LLM scoring | | Python 3.8+ | Local | All SEA scripts | | NumPy | `pip install numpy` | Embedding cache |
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.