llm-wiki-manager

LLM Wiki Manager

A Claude Code skill for building and maintaining a personal LLM-managed wiki — a persistent, compounding knowledge base where the LLM does all the writing, cross-referencing, and bookkeeping while you curate sources and ask questions.

🇹🇷 Türkçe için README.tr.md

---

Quick Start

git clone https://github.com/sametbrr/llm-wiki-manager ~/.claude/skills/llm-wiki-manager

Start a new Claude Code session in your research folder:

mkdir ~/research/my-topic && cd ~/research/my-topic && claude
> "Set up an LLM wiki here. Topic: history of nutrition science."

---

Features

Instead of RAG — where the LLM rediscovers answers from raw documents on every query — this pattern has the LLM compile raw sources into a persistent, interlinked markdown wiki. Each new source enriches existing pages. Cross-references are built eagerly. Contradictions are flagged. Knowledge compounds over time.

Implements Karpathy's LLM Wiki pattern as a full Claude Code skill with 8 operating modes (including multi-wiki routing), 5 idempotent Python scripts, 8 page templates, and 11 reference documents.

Without this pattern          With this pattern
────────────────────          ──────────────────
Query 1 → re-read 50 docs     Query 1 → read compiled wiki (already synthesized)
Query 2 → re-read 50 docs     Query 2 → read updated wiki (cross-refs already there)
Query 3 → re-read 50 docs     Query 3 → read updated wiki (contradictions already flagged)

---

Requirements

• Claude Code or any agentskills.io-compatible agent
• Python 3.9+ (stdlib only, for the 5 included scripts — no pip install needed)

---

Installation

Option 1 — git clone (recommended)

git clone https://github.com/sametbrr/llm-wiki-manager ~/.claude/skills/llm-wiki-manager

Option 2 — GitHub CLI (requires gh CLI v2.90+)

gh skill install sametbrr/llm-wiki-manager

Option 3 — .skill file

curl -L -o llm-wiki-manager.skill \
  https://github.com/sametbrr/llm-wiki-manager/releases/latest/download/llm-wiki-manager.skill
unzip llm-wiki-manager.skill -d ~/.claude/skills/llm-wiki-manager

After installing, start a new Claude Code session. The skill loads automatically when relevant.

---

Usage

The skill auto-detects which mode applies from natural language. No slash commands needed.

Modes

Full walkthrough

# 1. Go to your research folder
mkdir ~/research/my-topic && cd ~/research/my-topic && claude

# 2. Bootstrap the wiki
> "Set up an LLM wiki here. Topic: history of nutrition science."

# 3. Drop a source
cp ~/Downloads/pollan-2008.pdf raw/

# 4. Ingest it
> "Ingest Pollan's In Defense of Food"

# 5. Ask questions
> "What does the wiki say about nutritionism?"

# 6. Health check (auto-saves dated report to wiki/reports/)
> "Lint the wiki"

---

The three-layer model

your-wiki/
├── CLAUDE.md          # Schema — conventions for this wiki (co-evolved over time)
├── raw/               # YOUR layer — immutable sources you curate. LLM reads, never writes.
└── wiki/              # LLM layer — all pages written and maintained by the LLM
    ├── index.md       # Content catalog (updated on every ingest)
    ├── log.md         # Append-only operation log (greppable)
    ├── hot.md         # Hot cache — most recently ingested sources and active references
    ├── sources/       # One summary page per ingested source
    ├── entities/      # People, organizations, places, products
    ├── concepts/      # Ideas, theories, frameworks, terms
    ├── notes/         # Filed-back query answers and loose pages
    └── reports/       # Auto-generated dated lint reports (wiki/reports/lint-YYYY-MM-DD.md)

Division of labor:

You almost never write wiki pages by hand. The LLM does the bookkeeping — that's what makes the wiki compound instead of collapse.

---

Core disciplines

1. LLM owns wiki/. You own raw/. No exceptions.
2. Every operation logs to log.md via append_log.py. Greppable: grep "^## \[" log.md | tail -20
3. Every new or updated page touches index.md via update_index.py. Stale index = wiki that feels lost.
4. Cross-reference aggressively. When a source mentions an entity that already has a page, update that page. Don't leave connections implicit.
5. Cite back to raw/. Every claim is traceable to a specific source file.
6. Flag contradictions, don't overwrite. New source disagrees with old claim? Both stay, marked with their source, with a > [!warning] Sources disagree callout.
7. Schema lives in CLAUDE.md. When a convention works, write it down. The next session starts informed.

---

What's inside

Scripts (Python stdlib, no dependencies, all idempotent)

Templates