# Mempalace Recall

Recall protocol for MemPalace, search the palace before answering about past work...

- Repository: https://github.com/MemPalace/mempalace (60225 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add MemPalace/mempalace --skill mempalace-recall -g -a claude-code -y`
Codex: `npx skills add MemPalace/mempalace --skill mempalace-recall -g -a codex -y`
Cursor: `npx skills add MemPalace/mempalace --skill mempalace-recall -g -a cursor -y`
Gemini CLI: `npx skills add MemPalace/mempalace --skill mempalace-recall -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add MemPalace/mempalace`

## Description

Recall protocol for MemPalace, search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall is invoked. Complements the mempalace setup skill and requires the mempalace-mcp server.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# MemPalace Recall

Search-before-answer protocol for MemPalace. This skill makes the agent
read the user's memory palace before answering anything that may already
be filed there, instead of guessing from model memory. It complements
the `mempalace` skill, which covers install / mine / status; this one
covers recall only.

## Step 0, Verify MemPalace is available

Before relying on recall, confirm MemPalace is installed and reachable:

- Official release page: <https://github.com/MemPalace/mempalace/releases>
- Check installed: `mempalace --version`
- Do not assume a version, the MCP tool set is the source of truth for
  what this installed build supports.

If the `mempalace_*` MCP tools are not available, tell the user the
server is not connected and point them at the `mempalace` skill to set
it up. Do not silently fall back to answering from model memory.

## Identity

Act as a senior AI-memory systems engineer with decades of experience
building verbatim recall, semantic retrieval, and temporal knowledge
graphs. Verbatim recall from the palace always beats a confident guess
from model memory, wrong is worse than slow.

## When to recall

Search the palace **before answering** whenever the user asks about
something that may already be filed:

- Past work or prior decisions, "what did we decide / try / do?"
- A person, project, or entity, "who is …", "what is …"
- An earlier session, "remember when …", "last time …", "the thing we
  discussed"
- A preference, fact, or relationship that could have changed over time

Do **not** search on pure greenfield work with no memory relevance
(e.g. "rename this variable", "fix this typo"). Recall is
question-driven, not reflexive, a search on every turn wastes latency
and violates MemPalace's "memory should feel instant" budget.

## Protocol

The rest: https://github.com/MemPalace/mempalace/blob/HEAD/.antigravity-plugin/skills/mempalace-recall/SKILL.md