菜单
Recall past decisions and learnings from the WikiBrain memory vault — across all projects, its archive, and git history. Use when the user asks what they decided/learned/know about something, whether they've hit a problem before, or to search their memory.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compact the WikiBrain memory vault back within its context budgets — merge, rewrite, and archive memories, applying only user-confirmed actions. Use when the user says "compact memory" or "clean up memory", or when more than a week has passed since the last `memory: compact` commit.
Set up the WikiBrain memory vault on this machine — adopt project memory dirs via symlinks, install the wikibrain skills, ensure the private remote. Use after cloning the vault on a new machine, when a new project's memory should be adopted into the vault, or when the user says "set up wikibrain".
Sync the WikiBrain memory vault — commit and push to its private GitHub repo. Use when the user says "sync memory", after a session saves memories worth keeping, or when another wikibrain skill lands changes.
| name | wikibrain-recall |
| description | Recall past decisions and learnings from the WikiBrain memory vault — across all projects, its archive, and git history. Use when the user asks what they decided/learned/know about something, whether they've hit a problem before, or to search their memory. |
VAULT = the repo this skill lives in (resolve the ~/.claude/skills/wikibrain-recall symlink; default ~/personal/WikiBrain). It holds every project's memory — search the whole vault; the current project is just one slug among all of them.
Work down the recall ladder until the question is answered:
grep -ril "<term>" "$VAULT/memory" — current facts, indexed per project in MEMORY.md.grep -ril "<term>" "$VAULT/archive" — compacted-out facts, true at the time they were archived.git -C "$VAULT" log -S "<term>" --oneline then git show — content that was rewritten or deleted.Try synonyms and related terms on each rung before moving past it. Done when every claim in the answer cites its source — file path (rungs 1–2) or commit (rung 3) — or all three rungs came up empty, which is itself the answer: it isn't in memory.
A fact that surfaced only on rung 2–3 but matters again is a candidate for re-promotion: offer to write it back as an active memory (format per GUIDELINES.md).