llm-wiki plugin
A Claude Code plugin for Obsidian: stores sources, compiles linked wiki pages and answers from the accumulated knowledge.
- 110 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The `SessionStart` hook runs a dependency-install script, and the plugin writes files and commits into the Obsidian vault.
- The `remove` command deletes the wiki directory and the `qmd` collection.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/ekadetov-llm-wikiDetects 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.
- The `SessionStart` hook runs a dependency-install script, and the plugin writes files and commits into the Obsidian vault.
- The `remove` command deletes the wiki directory and the `qmd` collection.
This is third-party code. Review the repository files before installing.
What it does
llm-wiki builds a persistent knowledge base inside an Obsidian vault using the Karpathy LLM Wiki pattern. Claude Code saves source material, turns it into linked wiki pages and answers questions from what has accumulated, citing pages through `[[wikilink]]`. Work runs through the `/llm-wiki:wiki` command. `init` creates the wiki structure, `ingest` stores a source in `raw/articles/`, `compile` reads uncompiled sources and writes source, concept and person pages, `query` answers from the wiki, `lint` finds dead links, orphan pages and stale pages, and `remove` deletes a wiki. The plugin commits changes to git by itself.
Who it is for. Obsidian users who collect notes and articles on a topic and want a connected wiki with answers and links.
Good fit when
- Articles and notes on one topic pile up in `raw/` without a connected picture.
- An answer from the collected material is needed with links to wiki pages.
- The wiki has grown and now contains dead links and orphan pages.
- A new topic lives in its own vault folder with git history.
Not a fit when
- The vault is outside `~/ObsidianVault/` or has no `03-Resources/` directory.
- The wiki is needed without git and without automatic commits.
- Notes live in another application, not in Obsidian.
Example request
Create a wiki on the topic "agent systems", save this article as a source and compile pages from it.Limitations
The plugin expects a vault at `~/ObsidianVault/` with a `03-Resources/` directory; other locations are not documented. Node.js 18 or newer and Git are required. The `SessionStart` hook installs the `qmd` and `marp-cli` dependencies when a session starts, which can take up to two minutes. The `ingest` command only saves a source; `compile` creates the pages. The last commit in the repository is dated April 2026.
How to disable. Run `claude plugin uninstall llm-wiki`: the plugin and its dependency cache are removed while wiki data in `~/ObsidianVault/` stays.
FAQ
How do I create the first wiki in llm-wiki?
Run `/llm-wiki:wiki init my-topic`. `~/ObsidianVault/03-Resources/my-topic/` gets `raw/`, `wiki/`, the `CLAUDE.md` schema, indexes and git tracking.
How does `ingest` differ from `compile`?
`ingest` saves a source to `raw/articles/` and creates no wiki pages. `compile` reads uncompiled sources, writes pages, updates the index and commits.
Is `qmd` mandatory?
No. Without it the plugin reads `index.md` for small wikis. With `qmd` you get hybrid BM25 and vector search, and the hook installs it at session start.
What does `lint` check?
Dead links, orphan pages, missing sections, contradictions, stale pages and index drift. The plugin fixes what it can on its own.
What remains of the wiki after removing the plugin?
The whole wiki. `claude plugin uninstall llm-wiki` removes the plugin and its dependency cache, while data in `~/ObsidianVault/` is preserved.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin that runs a Karpathy-style wiki on Logseq or Obsidian and splits knowledge into memory rules and a deep wiki
An Obsidian vault template where an agent follows a CLAUDE.md schema to compile sources into a linked wiki and extend it.
Claude Code plugin for a personal wiki per Karpathy's pattern: the agent grows pages from sources and answers with citations.
A plugin that turns PDFs, articles and notes into a shared markdown wiki that agents search, cite and keep growing
A CLI that creates an Obsidian-ready Markdown vault and installs four skills so an agent maintains the knowledge base.
Turns session history of Claude Code, Codex, Cursor and Gemini CLI into a searchable wiki on Karpathy's LLM Wiki pattern, locally
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| llm-wiki (this card) | no | 110 | |
| LLM Wiki Compiler | no | 331 | compiles a wiki from notes or a codebase; llm-wiki works only inside an Obsidian vault and separates saving a source from compiling pages |
| claude-obsidian | no | 16,397 | turns an Obsidian vault into a knowledge base through a skill set; llm-wiki maintains separate topic wikis through `/llm-wiki:wiki` |
README in short
The repository holds a plugin with the `/llm-wiki:wiki` command, a `wiki` skill with compilation and frontmatter-schema guides, a dependency-install hook and a `lint-wiki.py` script. In the vault `raw/` holds immutable sources and `wiki/` holds model-owned pages.