brain-searchlisted

# Second Brain retrieval The user keeps one private Markdown vault. It is the same vault in every project and every session. This skill is how you read it. Retrieval is targeted: find the few notes that answer the question, then read those notes. Never load the vault in bulk. It is private, most of it is irrelevant to any single task, and a dump puts all of it in the transcript. ## Use this when - The task turns on an earlier decision, its reasoning, or how it turned out. - The task names a person, meeting, project, lesson learned, or an open action the user may have written down. - The user says "my brain", "my notes", "my vault", or asks what they already recorded about something. Skip it when the current repository, the open files, or the conversation already answer the question. An unrelated coding task is not a vault query. ## The vault Resolve the vault path as `${CLAUDE_PLUGIN_ROOT}/STANDARD.md` §7 describes, and read it once per session — not once per search. Every path you pass is absolute, under that root; your working directory is a code project, so a relative path resolves against the wrong tree. The layout and the eight note types are in that same document, §2 and §3. Read it if you have not this session; the type names and their frontmatter are what make a search precise instead of a scan. ## Retrieval Work down this list and stop as soon as you can answer. 1. **Index first, when the question implies a directory.** `projects/index.md`, `people/