Use when the user wants to check or clean up the vault's consistency/hygiene, e.g. "lint my vault", "find broken links", "any duplicate or empty notes", "check my frontmatter", "audit my tags", "update my MOCs", "sync my maps of content". Reports structural/metadata problems (broken links, dupes, empty notes, frontmatter drift, tag-taxonomy drift, out-of-date MOCs) and fixes the safe ones with approval. Never writes note prose.
Use when the user wants their notes on objective subject matter (math, physics, CS, philosophy, etc.) checked for things that are actually wrong, e.g. "audit my MSM notes for errors", "fact-check my philosophy of mind notes", "is anything in my
Use to set up (or re-profile) a vault for the vault-mind skills, e.g. "set up vault-mind", "init my vault", "vault-mind isn't finding my notes", "re-detect my vault structure". Inspects the user's Markdown vault, infers its layout and frontmatter schema, confirms with the user, and writes a vault profile that every other vault-mind skill reads. Run this once before using quiz/feynman/ask/etc. Writes only the profile file, never touches note content.
Use when the user wants to find concepts they should write notes for but haven't, e.g. "what notes am I missing on reinforcement learning", "find gaps in my philosophy notes", "what should I write next". Surfaces terms/concepts referenced across their notes and readings that have no note yet, ranked as a next-write queue. Never writes the notes for them.
Use when the user asks a question about the contents of their own vault, e.g. "what did I conclude about functionalism", "what do my notes say about lag time in MSMs", "which books did I rate above 8", "summarize what I know about Koopman operators". Answers strictly from their notes/readings, cited to the source files. Read-only, never writes.
Use when the user wants to find non-obvious connections between their existing notes, e.g. "what connects to my Koopman operator note", "find links I'm missing in my philosophy of mind notes", "connect my ML and chemistry notes". Surfaces conceptual overlaps that aren't wikilinked yet and suggests where THEY might draw the link. May insert a wikilink they approve; never writes note prose.
Use when the user wants to talk through something they just read (or are reading) to form their own view before writing a note about it, e.g. "let's discuss What Is It Like to Be a Bat", "I just finished Hyperion, discuss", "help me think through the Chinese Room argument". A Socratic partner that asks probing questions and challenges them; it does NOT hand them a take or write the note. This is for open-ended discussion of a reading to form a view; if they instead want to drill the formal structure of a single argument (reconstruct its premises, attack and defend it), that's /vault-mind:socratic-philosophy, not this.
Use when the user wants the actual source document for a reading pulled down locally so the agent can read it directly, e.g. "fetch the source for Epiphenomenal Qualia", "download the papers in my philosophy of mind list", "grab a local copy of the VAMPnets paper", "fetch everything I haven't downloaded yet". Resolves the reading's online-source URL, downloads a publicly available copy into the assets dir, and verifies it. Downloads source files only, never writes note prose.