Menu
Mine a project directory into the mempalace corpus (drawers, rooms, wings)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diagnose mempalace setup (config, palace path, MCP, FTS/index health)
List or inspect people/project entities tracked in the mempalace graph
Hybrid search over the mempalace corpus (BM25 + vectors + optional graph)
Show mempalace palace status (drawers, wings, rooms, health)
Trace a file, function, or line back to the agent session that produced its current commit
List recent git commits linked to agent sessions, optionally filtered by branch or repo
| name | mine |
| description | Mine a project directory into the mempalace corpus (drawers, rooms, wings) |
| argument-hint | [path] [--wing name] |
| user-invocable | true |
The user wants to mine project content into mempalace: $ARGUMENTS
Run mpr mine <path> (or call MCP mempalace_mine when available). Prefer CLI when path is large.
Populate the palace with searchable drawers so future recall / search has real corpus.
$ARGUMENTS (default: current project root).--wing <name> or infer from directory basename.mpr mine <path> --wing <wing> for progress and lock safety.mempalace_mine is available and path is small, call it with path, optional wing.WRONG -- mining node_modules / .git / build dirs without excludes:
// mpr mine . with no skip of vendor trees
RIGHT -- rely on default skip dirs, or pass excludes if the CLI supports them:
// mpr mine ./src --wing myapp
WRONG -- mining secrets (.env, credentials):
// mining paths that contain private keys or tokens
RIGHT -- mine source/docs only; keep secrets out of the palace.
If neither CLI nor MCP mine is available:
mpr is on PATH (mpr --version).mpr init <dir> first if no palace exists./mcp for mempalace connection.See
_shared/TROUBLESHOOTING.mdfor more.