Save to brain, file in the brain, add to brain, record findings, save this plan, document this in the brain, write up these findings, put this in the knowledge base. Use whenever the user wants to persist a document, plan, or finding into their long-term knowledge vault at ~/brain.
Persist documents, plans, and findings to the long-term knowledge vault at ~/brain.
The vault is an Obsidian knowledge base — wiki-style markdown with YAML frontmatter and [[wiki-links]] between notes. Treat it as a connected graph, not a flat pile of files.
For proactive capture of what the agent learned or did during a task, use the memory skill instead — this skill is for deliberate writes the user has asked for.
Read ~/brain/README.md. It is the authoritative source on directory layout, file format, frontmatter schema, tag conventions, and the git workflow. This skill defers to that file — do not re-derive structure from memory.
Read ~/brain/README.md
If the README and this skill ever disagree, the README wins.
~/brain/README.md to refresh the current structure and link syntax.findings/, plans/, documents/) using the table in the README. If the user explicitly said "memory" or this is a proactive capture, stop and use the memory skill instead.[[fastapi-middleware-order]].Glob ~/brain/**/*<keyword>*.md and a Grep of the topic. Two goals:
[[...]] in the body and in a ## Related section.git -C ~/brain pull --rebase.type. Use [[wiki-links]] to reference other brain notes — never plain paths. End non-trivial notes with a ## Related section.<type>: <action> <slug>). Stage only the files you touched.Glob/Grep, Read it, use Edit for targeted changes, bump date only if the change is substantive.done or abandoned, a draft finding that's been superseded): change the frontmatter status field instead of moving the file. The vault is small enough that there's no separate Archive directory yet.memories/ from this skill — that path belongs to the memory skill.