LLM Wiki

Build and maintain a persistent, compounding personal knowledge base as plain Markdown files. The wiki is not a chat transcript and not a disposable RAG cache: it is a curated memory layer where raw sources, synthesized pages, cross-links, contradictions, and reusable answers accumulate over time.

Use this skill when the user asks to create or maintain a personal wiki, ingest sources into the wiki, query accumulated knowledge, audit wiki quality, or turn research into durable notes.

Operating Contract

• Wiki root resolution order: explicit user path > WIKI_PATH env var > remembered path in ~/.llm-wiki > current working directory (when it already contains SCHEMA.md, index.md, and log.md) > ~/wiki.
• The wiki must remain readable in Obsidian, VS Code, and plain text tools.
• Raw sources are immutable after capture. Fix interpretation in synthesized pages, not in raw/.
• Every durable wiki action updates both navigation (index.md) and history (log.md).
• Prefer fewer, stronger pages over many thin pages.
• Preserve uncertainty. Use confidence, contested, contradictions, and explicit open questions instead of smoothing over weak evidence.
• Do not mass-update 10+ existing pages without explaining the intended change set first, unless the user explicitly asked for autonomous bulk maintenance.
• Treat the wiki root as a dedicated wiki directory. Do not initialize into a non-empty unrelated directory unless the user explicitly approves it.
• Only add helper scripts for deterministic, repetitive work. For this skill, bundled scripting is justified for wiki bootstrap (scripts/init-wiki.sh), but ingest/query/lint remain mostly agent-driven until scale proves more tooling is needed.

Directory Structure