obsidian-wikis

A starter template for an Obsidian vault that holds multiple llm wikis — knowledge bases where an LLM turns raw sources into curated, cited wiki pages, following Karpathy's llm-wiki pattern.

Unzip it, open a terminal at the root, and scaffold as many wikis as you want. Each is an isolated sub-directory with its own sources, pages, log, and rules — sharing one set of tools, skills, and guardrails.

Layout

.claude/ .gemini/ .agents/     harness config (symlinks into assets/)
.obsidian/                     Obsidian settings, themes, plugins
assets/harness-related/
  AGENTS.md                    canonical rules, symlinked into every wiki
  tools/                       Python tools + hook guards (uv, PEP 723)
  skills/vault/                skills for the vault root (new-wiki)
  skills/wiki/                 skills inside a wiki (the other 7)
  vault/{claude,gemini}/       hook settings for vault-root sessions
  wiki/{claude,gemini}/        hook settings for wiki sessions
<wiki-name>/                   each llm wiki you create
  raw/{to-process,processed,flagged}
  wiki/<subdir>/index.md
  wiki/index.md, wiki/log.md
  RULES.md

Quick start

From the vault root:

uv run .agents/tools/new-wiki.py <name> \
  --subdirs <sub1> <sub2> ... \
  --description "one line"

Then open a session inside the new wiki (cd <name>) to write the subdir descriptions, drop sources into raw/to-process/, and ingest them.

Skills

At the vault root — new-wiki only: scaffold a new llm wiki.

Inside a wiki:

Skill	Purpose
wiki-ingest	turn a file in raw/to-process/ into cited wiki pages
wiki-query	answer a question from existing pages, with citations
wiki-health	fast structural check (frontmatter, links, indexes)
wiki-lint	deeper LLM audit (orphans, contradictions, stale content)
wiki-update	refresh wiki/index.md and wiki/log.md
wiki-graph	build the wikilink knowledge graph
wiki-stats	page counts, raw pipeline state, type breakdown

Works with any harness that reads the Agent Skills standard — Claude Code, Gemini CLI, and others.

Guardrails

Enforced by hooks, not by trusting the model:

• Wiki isolation — a session writes only into the wiki it was opened in. Writes into a sibling wiki, or into any wiki from a vault-root session, are denied for every tool (Write, Edit, Bash). Scaffolding a new wiki from the root still works.
• Immutable sources — files under raw/ are never edited or deleted in place; only moved between to-process/, processed/, and flagged/.
• Page validation — pages are checked on write for mandatory frontmatter, a valid type, resolvable wikilinks, and citations that point at a real source file.

Note: skill discovery scans the whole vault tree, so another wiki's skills may appear available in a session that shouldn't use them. Availability is not permission — the guards, not the skill list, decide what can be written.

Requirements

• uv — tools declare dependencies via PEP 723 inline metadata; always uv run, never bare python.
• Obsidian (optional) — the vault works as plain Markdown either way.