Obsidian Knowledge Agent plugin
A plugin that files PDFs, slides and links into Obsidian notes and proposes edits to its own rules after every run
- 206 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Creates, moves and rewrites vault files, and clean commits changes and pushes
- Self-evolution hooks append the run journal to `.agents/learned/` without prompting
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/obsidian-knowledge-agentDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Creates, moves and rewrites vault files, and clean commits changes and pushes
- Self-evolution hooks append the run journal to `.agents/learned/` without prompting
This is third-party code. Review the repository files before installing.
What it does
The plugin runs in Claude Code and Codex and turns raw material into notes in an Obsidian vault: PDFs, slides, syllabi, papers, link lists. Before writing, the agent reads how the vault is already organized: folders, file names, frontmatter. Then it picks the amount of work. A link or a thought becomes one note, a few sources give a couple of notes with a short index page, and a whole course or book gets a full scaffold with indexes, navigation, a quality pass and a concept-graph canvas. The plugin ships the obsidian-knowledge skill, 12 commands prefixed `/obsidian-knowledge:` (setup, capture, ingest, research, log, polish, refactor, doctor, clean, reflect, evolve, help) and self-evolution hooks. After a run, reflect writes lessons to a journal and the agent turns proposed rule changes into a git diff. The human approves it with evolve, and the learned conventions in `.agents/learned/` are picked up on the next run.
Who it is for. People who keep course notes and work notes in Obsidian and want an agent to file PDFs, slide decks and links into the vault using its own conventions.
Good fit when
- An Inbox holds a syllabus, a paper PDF and lecture slides, and you want structured notes with indexes built from them
- You need to save a link or a thought fast: the note lands in the right folder with tags and links to related notes
- The vault has grown, and doctor should find broken links, orphan notes and missing frontmatter
- The agent keeps formatting notes in a way you dislike, and you want the correction to become a standing rule through reflect and evolve
Not a fit when
- Your notes live outside Obsidian: wikilinks, frontmatter and JSON Canvas files are built for it
- The vault must stay read-only for the agent: the plugin creates and moves files, and clean commits and pushes
- You only need a one-off summary of a single document: a plain request does that without a 12-command plugin
Example request
Take the syllabus from Inbox and build structured notes in my vault, with an index and a concept graphLimitations
- The plugin installs in Claude Code and OpenAI Codex through a marketplace. For other agents, `install.sh` only seeds rule files and learning state into the vault folder, with no commands or hooks.
- The agent creates and moves files, and clean commits and pushes, so the vault should live under git.
- The School, ML and Quant folders are a starting layout for an empty vault. In a working vault the agent adapts to the folders already there.
- The run journal is appended without prompts, while rule changes go only through a diff for approval.
How to disable. Disable and remove the plugin with the Claude Code or Codex plugin manager. The rule files in `.agents/` and the learning state in `.agents/learned/` live in the vault itself and are removed by hand.
FAQ
How do I install Obsidian Knowledge Agent in Claude Code?
Two commands: `/plugin marketplace add Michael-OvO/obsidian-knowledge-agent` and `/plugin install obsidian-knowledge@obsidian-knowledge-agent`. Then run `/obsidian-knowledge:setup` in the vault folder; it works for an empty folder and for an existing vault.
How is capture different from ingest?
capture saves one clean note in the right folder. ingest builds notes from Inbox or from the sources you point at, at the right level: from a couple of notes to a full course scaffold.
How does the plugin learn from my corrections?
After a run, reflect journals what happened and proposes rule changes as a git diff. Rules change only after you approve the diff with evolve. Accepted conventions live in `.agents/learned/`.
Does it work without Claude Code and Codex?
Partly. `install.sh` seeds rule files and learning state into any folder, and any agent can read them as instructions. The plugin commands and hooks are not part of that setup.
What do the doctor and clean commands do?
doctor health-checks the vault: broken links, orphan notes, missing frontmatter. clean commits changed notes, clears the processed Inbox with your approval and pushes.
Discussion
No questions or reviews yet.
Related
PluginsA plugin and skill set that turns an Obsidian vault into a knowledge base with sources, links and grounded answers
Obsidian skills
Obsidian Skills
Skills for agents working with Obsidian: Markdown with wikilinks, Bases, JSON Canvas, Obsidian CLI, Defuddle and Knap
Persistent agent memory in an Obsidian vault: saving decisions, search, research and background vault upkeep
A skill set that lets an agent run a personal Obsidian wiki: it compiles knowledge from documents and past sessions and answers with citations
A Claude Code plugin that builds a knowledge system of markdown files from a conversation with you: folder structure, note templates, a processing pipeline and
Agent Client for Obsidian
Agent Client
An Obsidian plugin that runs Claude Code, Codex and other agents via the Agent Client Protocol right inside your notes vault
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Obsidian Knowledge Agent (this card) | no | 206 | |
| Obsidian skills | no | 50,894 | skills for Obsidian formats: wikilinks, Bases, Canvas, with no rule self-learning loop |
| claude-obsidian | no | 16,226 | a plugin for a sourced knowledge base with answers over it, while Knowledge Agent focuses on turning study material into notes |
README in short
The README opens with a before and after: a plain agent dumps a summary into one file at the root, while the plugin files the note in the right folder, matches your frontmatter and links related notes. Next come two install paths, a table of 12 commands and a diagram of the loop: recall rules, process material, reflect, approve changes. Separate sections cover the note style and the concept-graph canvas for collections of three or more notes.