capture
Quickly save something as a single clean note in the right place — a link, a thought, an article, a snippet
Set up this folder as a knowledge vault — adapts to an empty folder or an existing vault
> /plugin marketplace add Michael-OvO/obsidian-knowledge-agent > /plugin install obsidian-knowledge@obsidian-knowledge-agent
How it fires
How this command gets triggered: by you, by Claude, or both.
/setupContext preview
What this command does when you run it.
Set up this folder as a knowledge vault — adapts to an empty folder or an existing vault
description: Set up this folder as a knowledge vault — adapts to an empty folder or an existing vault argument-hint: [optional: domains/branches you want, e.g. "ML, Quant, Research"]
Set up the current folder as an Obsidian Knowledge Agent vault. **Detect first, then do the least surprising thing.** Always idempotent — never clobber anything that exists.
**Step 0 — Detect the folder and tell me which mode you're in:**
`.agents/learned/` → **ADOPT** (fit what's there, fill only the gaps).
Then run the matching mode:
Don't re-create anything. Report status in a couple of lines — the branches, how many items are in `Inbox/`, the last `journal.md` entry — and route me to work: *"Inbox has 3 items — want me to `:ingest`? Or tell me what to capture."* Stop there.
1. **Read, don't impose.** Map the existing top-level folders, naming style, and the frontmatter on a few notes. Treat that as the vault's conventions — do **not** add new branch folders or rename anything. 2. **Fill only the gaps.** Create `.agents/learned/` (`journal.md`, `conventions.md`, `examples.md`, a `skills/` folder) only if missing; add `Inbox/` and a `Dashboard.md` map-of-content that links the **existing** branches. Never overwrite existing files. 3. **Seed conventions for review.** Write what you detected (naming, frontmatter, folder shape) into `.agents/learned/conventions.md` as a proposed starting point, and show me the diff before committing it. 4. **Commit** the additions, then point me at `/obsidian-knowledge:help`.
1. **Branches.** Create top-level branch folders — from `$ARGUMENTS` if given, otherwise propose a small default (a shared `References/` plus one or two domains) and confirm with me before creating. Give each branch an `_index.md`. 2. **Learning state.** Create `.agents/learned/` with `journal.md`, `conventions.md`, `examples.md`, and a `skills/` folder — seed empty starters. 3. **Inbox + dashboard.** Create `Inbox/` and a `Dashboard.md` map-of-content that links the branches and explains the workflow in a line or two. 4. **Commit** the scaffold, then point me at `/obsidian-knowledge:help` and suggest dropping a first source into `Inbox/`.
Talk to your vault. It does the rest. You drop it in. It files, it teaches, and it remembers how you like your notes. Point any agentic assistant at your Obsidian vault and talk to it — "save this link", "organize my inbox", "ingest the syllabus in Inbox".
Repo: Michael-OvO/obsidian-knowledge-agent
Quickly save something as a single clean note in the right place — a link, a thought, an article, a snippet
Tidy and sync — commit changed notes, clear processed Inbox (with approval), and push
Check vault health — broken links, orphans, missing frontmatter, MISSING placeholders — and propose fixes
Review and approve the agent's proposed updates to its own learned rules
Show everything the Obsidian Knowledge Agent can do, with every command and an example
Turn material into notes at the right altitude — a quick capture, a small collection, or a full build