By ignromanov
Maintain a persistent, compounding knowledge base in Obsidian using four specialized LLM agents that research topics from web sources, capture raw inputs with cryptographic provenance, answer questions with cited wiki links, and auto-audit vault health for orphans, contradictions, and schema drift.
You are wiki-advisor — senior consultant who has read the entire vault and remembers its structure. Simon-Willison style: confident answers, but always with citations. You'll say "we don't know" instead of hallucinating.
You are wiki-curator — librarian-archaeologist. Maggie-Appleton evergreen-discipline + Andy-Matuschak atomicity + ADR-archivist rigor. Meta-expert who looks at the system as an object.
You are wiki-researcher — a field researcher-archivist with Karpathy's instincts. You compile knowledge once and don't re-derive it. You love provenance the way an engineer loves logs.
You are wiki-scribe — discreet court-reporter. Capture verbatim, file properly, no interpretation. Complete opposite of Researcher: passive inbound, no editorial judgment.
This skill should be used when wiki-advisor needs to answer a user question by searching the wiki, retrieving cited claims, and composing an answer with [[wikilink]] references. Triggers on "what do we know about X", "what did we decide", "answer from the wiki", "find in vault".
This skill should be used when wiki-curator needs to perform a read-only health check of the vault, scanning for orphans, stale pages, source drift, contradictions, and tree-topology violations. Triggers on "audit wiki", "check health", "find issues", "wiki diagnostic".
This skill should be used when an agent needs to ingest a source (URL, YouTube, GitHub, PDF, clipboard, session log) into the vault. Triggers when wiki-scribe or wiki-researcher needs to "capture", "save source", "intake", "file URL", or "hash and store".
This skill should be used when bootstrapping a brand-new LLM Wiki vault — creates dir tree, seeds wiki.config.md, CLAUDE.md, hot.md, .gitignore. Invoked via /wiki:init slash command. Triggers on "init wiki", "create new vault", "scaffold knowledge base".
This skill should be used when wiki-curator needs to apply auto-fixes for structural violations (orphans, missing fields, hot.md updates) and propose semantic fixes (contradictions, supersession, hub splits) with user confirmation. Triggers on "fix wiki issues", "auto-resolve", "split hubs", "promote drafts", "update hot.md".
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
The Problem | Install | See It Work | Quick Start | Architecture | Skills | Agents
LLMs lose all context between sessions. RAG systems re-derive knowledge from raw documents on every query, spending tokens to rediscover what was already known. In 2025, Andrej Karpathy proposed a different approach: have the LLM incrementally build and maintain a persistent wiki -- structured, interlinked markdown that compounds over time. The idea sparked a 400+ comment discussion drawing on the Zettelkasten tradition and digital garden movement.
This plugin turns that idea into a working system. It is a Claude Code plugin with 4 task-oriented agents, 7 internal workflow skills, 2 slash commands, and 27 utility scripts that automate the full capture / research / answer / audit / maintain loop inside an Obsidian vault. Knowledge is compiled once and kept current -- not re-derived on every query.
[!IMPORTANT] Trust and transparency
- Local-only: All data stays in your Obsidian vault on your machine. No cloud sync, no external storage.
- No telemetry: No analytics, no usage tracking, no phone-home behavior of any kind.
- Network access: Only capture scripts (
capture-url.sh,capture-youtube.sh,capture-github.sh) make network requests, and only to URLs you explicitly provide.- What it creates: Files in
raw/,wiki/,index.md,log.md,wiki.config.md, and.obsidian/config -- all inside your vault.- Uninstall:
/plugin remove llm-obsidian-wiki@ignromanov-- your vault data remains untouched.
Prerequisites: Claude Code, Obsidian, Obsidian CLI
From the Claude Code plugin marketplace:
# Add the marketplace source
/plugin marketplace add ignromanov/llm-obsidian-wiki
# Install the plugin
/plugin install llm-obsidian-wiki@ignromanov
Or load directly from a local clone:
git clone https://github.com/ignromanov/llm-obsidian-wiki.git
claude --plugin-dir /path/to/llm-obsidian-wiki
$ claude
> /wiki:init
What is the project/wiki name? ml-research
Which page types? (all 10 selected)
Which raw source directories? (defaults: knowledge, specs, meetings, docs, external, inbox)
Which capture tools are installed? defuddle, trafilatura
Wiki vault "ml-research" created successfully.
Files: CLAUDE.md, wiki.config.md, index.md, hot.md, log.md
Next: open the vault in Obsidian, add your first source.
> "research karpathy llm wiki pattern"
[wiki-researcher]
Capturing: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
Saved: raw/external/2026-04-11-karpathy-llm-wiki-pattern.md
Compiling wiki pages...
Created: wiki/sources/src-karpathy-llm-wiki-pattern.md
Created: wiki/concepts/llm-wiki-pattern.md (confidence: high, 3 sources)
Created: wiki/concepts/compounding-knowledge.md
Updated: index.md, hot.md, log.md
> "how does compounding knowledge differ from RAG?"
[wiki-advisor]
Searching wiki... 3 pages found, reading 2...
RAG re-derives answers from raw documents on each query, paying full token
cost every time. The LLM Wiki pattern ([[llm-wiki-pattern]]) compiles
knowledge once into structured [[compounding-knowledge]] pages maintained
incrementally. Subsequent queries read the compiled wiki instead of
re-processing raw sources.
Sources: [[src-karpathy-llm-wiki-pattern]], [[compounding-knowledge]]
> "clean up the wiki"
[wiki-curator]
Running health checks...
✓ No orphaned pages
✓ No broken wikilinks
⚠ 1 stale page detected: wiki/concepts/compounding-knowledge.md (90 days)
Auto-fixed: index drift resolved
Report saved: log.md
npx claudepluginhub ignromanov/llm-obsidian-wiki --plugin llm-obsidian-wikiLLM Wiki — persistent, compounding knowledge base inside Obsidian. Ingest, compile, query, lint, and remove knowledge base wikis. Based on Karpathy's LLM Wiki pattern.
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows
LLM-maintained knowledge base skill — structured wiki with Obsidian, milestone-based source clustering, proactive write-back, and autonomous lint
Claude + Obsidian knowledge companion. Sets up a persistent, compounding wiki vault (Karpathy's LLM Wiki pattern). v1.7 "Compound Vault" + v1.8 methodology modes close 5 of 5 priority gaps from the May 2026 compass artifact. Ships: substrate alignment with kepano/obsidian-skills, default Obsidian CLI transport, hybrid retrieval (contextual prefix + BM25 + cosine rerank per Anthropic's Sept 2024 research), per-file advisory locking for multi-writer safety, pre-commit verifier agent, AND methodology modes (LYT / PARA / Zettelkasten / Generic) for first-class organizational support no other Claude+Obsidian competitor offers. v1.7.x audit closure: every BLOCKER + HIGH + MEDIUM + LOW finding from the v1.7.0 audit is CLOSED or DEFERRED-with-rationale. Optional DragonScale Memory extension (log folds, deterministic addresses, semantic tiling lint, boundary-first autoresearch).
Personal LLM-managed wiki: ingest sources, cross-reference pages, query with citations, and lint your markdown knowledge base
LLM-maintained personal wiki skills for Claude Code. Implements Karpathy's LLM Wiki pattern — persistent, compounding knowledge base for research, codebase documentation, or any long-term knowledge accumulation.