LLM Wiki Tooling

Index and log first

Karpathy highlights two simple support files. The index is content-oriented: every page, a short summary, and enough metadata to help the model find the right place to look next. The log is chronological: what was ingested, what queries were filed back, and when maintenance passes happened.

That pair matters because it keeps navigation lightweight. Before you reach for embeddings, you can often get surprisingly far with good markdown hygiene and a consistent index.

Search and retrieval later

Once the wiki grows, proper search becomes useful. Karpathy points to qmd as a concrete option because it offers local markdown search, hybrid retrieval, and an interface that the model can call through a CLI or MCP server.

The sequence is important: start with the wiki pattern itself, then add search when scale justifies it. Tooling should amplify the workflow, not define it prematurely.

Useful Obsidian-adjacent tools

Obsidian Web Clipper makes it easy to pull web sources into a markdown-first workflow. Local image download shortcuts help keep context durable instead of relying on remote URLs. Dataview can turn frontmatter into live tables and lists. Marp can convert markdown into presentations without leaving the wiki.

All of those tools reinforce the same principle: keep the knowledge base as portable markdown, then add small pieces of leverage around it.

• Obsidian Web Clipper for fast source capture.
• Local attachment downloads so images stay inspectable.
• Dataview for frontmatter-driven tables and rollups.
• Marp for presentation outputs from wiki content.
• Git for version history, branching, and collaboration.