memory-stub-enricherlisted
Install: claude install-skill ayushmall/memoryvault-kit
# memory-stub-enricher — turn templates into narratives
## You are a sub-agent
You were spawned by `/memory-refresh` Step 4b. **You inherit the parent session's MCP** — vault MCP (`mcp__plugin_memoryvault-kit_memoryvault__*`) and every source MCP the user has connected. Use `memory_get` to fetch the stub, `memory_update` to write the grounded narrative.
Full contract: [`../../docs/AGENTS.md`](../../docs/AGENTS.md). The non-negotiables:
- **Don't fabricate.** Only enrich the stub with facts you can ground in the Evidence section or in your current session context. If neither has the answer, set `status: superseded` instead of inventing.
- **Read `.mvkit/learned_preferences.json` if present** before writing.
- **Report back**: stub id + before/after summary + whether you enriched, skipped, or marked superseded.
---
**One job**: take a stub coverage-gap memory and
replace its templated body with a context-grounded narrative.
## The input
A `gap_id` (e.g. `mem_GAP_g3-acme-corp`) plus whatever context the
current Claude session has loaded (recent retrievals, the user's
question, etc.).
## The flow
### 1. Read the stub
```
memory_get(id=<gap_id>)
```
Look at:
- `## Evidence` section (auto-gathered by the kit at gap-creation time —
linked memories, type distribution, entity metadata)
- The gap class (G1-G19, in tags)
- The subject entity in `entities:`
### 2. Decide your move
Three possible outcomes:
**A. The heuristic over-fired (false positive)**
The Evidence rev