memorblisted

# Memorb (Gateway Skill) > **CRITICAL**: Primary routing hub for the vault. Every file operation must strictly follow these instructions and sub-skill routing without exception. ## Instruction Priority 1. **Explicit User Instructions** (highest) 2. **Memorb & Routed Sub-skills** (overrides default agent behavior) 3. **Default Agent Behavior** (lowest) ## Core Rules Before performing any file operation: 1. Read this gateway file. 2. Read `SKILL.md` for **every matching sub-skill** in the routing table below. 3. All write operations must adhere to `memorb-conventions` (paths, naming, frontmatter). 4. Load multiple sub-skills if needed (e.g., transcript processing = `recording-transcription` + `memorb-ingest`). ### Ownership boundary **memOrb may read anything the user points it at; it writes only inside `memorbs/`.** No exceptions — this binds extensions too. Reading is safe: no state change, no surprise. Conditional *writing* is where the trouble lives. The moment a skill says "write to the reference folder if it exists", the same operation produces three different outcomes depending on a coincidence of folder naming — it writes for one user, silently skips for the user who numbered their folders, and does nothing for the user who has none. That is worse than either owning the folder or never touching it. So memOrb grows exactly one folder in the user's vault: `memorbs/`. Delete it and the vault is clean. ## Skill Router Table Core skills reside in `skills/core/{name}/S