memory-savelisted
Install: claude install-skill ayushmall/memoryvault-kit
# memory-save
When the user wants to persist something to their MemoryVault, use the
`memoryvault.memory_save` MCP tool.
---
## First: read the coverage-gap feedback memories
Before saving, **search for active gap memories**:
memory_search type=feedback tags=coverage-gap status=active
These are gaps the kit's coverage analyzer or low-confidence retrievals
detected — concrete authoring tasks waiting to be filled. Each one is
a feedback memory with the gap class (G1–G14), the subject entity, an
`## Evidence` section (auto-gathered: entity metadata, linked memories
with dates/types, type distribution), and a `## How to enrich this gap`
section that tells *you* what to do.
There are three actions you can take on a gap, in priority order:
### 1. Enrich the stub if it's still templated
If the gap memory has `tags: [...stub-enrich-me]` and `enriched: false`,
the auto-gathered evidence is sitting there waiting for you to turn
into a narrative. **You already have everything you need**:
- The `## Evidence` section lists the entity's linked memories, type
distribution, and metadata
- Whatever context the current session has loaded
Call `memory_update` to:
- Rewrite `title:` so it reflects the actual situation (not the template)
- Rewrite the body to say: *what we know, what's missing, how to fill it*
- If the heuristic over-fired (the evidence shows the gap doesn't
apply), set `status: superseded` with `tags: [...heuristic-over-fired]`
and include a detector-fix recom