everme-memorylisted
Install: claude install-skill EverMind-AI/EverMe
# What it gives you
When this plugin is loaded, the host has these MCP tools available:
| tool | input | output (markdown / JSON) |
|-----------------|----------------------------------------------------------------|-------------------------------------------------------------|
| `mem_context` | `{ forceRefresh? }` (`query` deprecated/ignored) | markdown Profile snapshot — Profile ONLY, never a search |
| `mem_search` | `{ query, topK? }` | markdown search results across all memory buckets |
| `mem_save_fact` | `{ fact \| messages, sessionKey?, flush? }` | `{ saved, accepted, status, extracted, profileUpdated, … }` |
| `mem_save_turn` | `{ role, text \| messages, sessionKey?, toolCallId?, flush? }` | `{ saved, accepted, status, messageCount, flushed, profileStatus, profileUpdated }` |
# Recommended usage
**Call these tools autonomously — the moment a trigger fires, not only
when the user explicitly asks you to "remember" or "recall".** Each
tool's MCP `description` also carries its trigger, so hosts that don't
surface the server `instructions` still get the same guidance.
**Dedupe with native injection first.** Some hosts inject
`<everme_profile>` at session start and `<everme_recall>` before each
prompt via native hooks. When a non-empty, relevant block is already in
your cont