obsidian-wiki
Maintaining project wikis is tedious and they quickly go stale.
Framework that lets an AI agent build and maintain an Obsidian vault as a persistent knowledge base, following Karpathy's LLM Wiki pattern: compile what you learn into interconnected markdown notes instead of re-asking the LLM or re-running RAG. Skills are plain markdown files any coding agent can run (Claude Code, Cursor, Windsurf, and others); a Python CLI adds setup, query, lint, and doctor commands plus multi-vault routing with @name overrides.
- Build structured Obsidian wikis from AI agent conversations
- Maintain project documentation automatically using LLM patterns
- Convert scattered notes into navigable knowledge bases
Maintaining project wikis is tedious and they quickly go stale. This framework lets AI agents build and maintain an Obsidian wiki using Karpathy's LLM Wiki pattern — turning AI conversations into persistent, navigable knowledge bases.
Developers and knowledge workers using Obsidian who want AI agents to automatically build and maintain structured project wikis.
https://github.com/Ar9av/obsidian-wiki
By Ar9av
How to Get It
pip install obsidian-wiki && obsidian-wiki setup --vault /path/to/your/vault
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me build structured Obsidian wikis from AI agent conversations
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Reddit
- This is Obsidian, a naturally occurring volcanic glass It forms when lava, rich — Reddit · 35623 pts
- We are Obsidian Entertainment, creators of AAA RPGs for over a decade including — Reddit · 15063 pts
- Anyone else uses Obsidian more like personal Pinterest / Wiki, than a hardcore p — Reddit · 281 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 3,180 GitHub stars; 23 contributors; last commit 8d ago; license MIT.
Things to check
- Recently discovered. Looks promising but has limited community feedback so far.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 3,180 GitHub stars; 23 contributors; last commit 8d ago; license MIT.