llm-wiki

name	llm-wiki
description	Use this skill whenever work is wiki- or knowledge-base-shaped—especially if the user says wiki, knowledge base, vault notes, or raw/ in this project. Trigger on words such as `ingest wiki`, `add to wiki`, `init wiki`, or `lint wiki`, updating or revising wiki pages, and on domain-specific questions that should be answered from the wiki (what we know about X, compare A and B, gaps, contradictions)—not off-wiki trivia. Do not use for generic chat, unrelated code or tooling, or file operations with no wiki intent.
metadata	{"author":"hsuanguo","version":"1.0"}

LLM Wiki

An LLM wiki that evolves with you. Based on Karpathy's LLM Wiki.

How to work

Use two phases: (1) gather context, (2) map the request into steps—each step is one operation with a dedicated reference file. Read that reference before executing the step.

1. Gather context

Infer intent from the user’s message (bootstrap, ingest, answer from the wiki, revise pages, lint, etc.) and state from the vault:

• Whether a wiki already exists at the target root (wiki/index.md and wiki/log.md).
• If it exists: skim wiki/index.md, tail wiki/log.md, and inspect raw/ when ingest, drift, or new sources matter.
• If uncertain about what a wiki structure looks like, ALWAYS run lwiki structure to get the information.

2. Map intention to one or more steps

Decompose the request into an ordered list of steps. Each step = a single primary operation. Open the matching reference for every step you will run; do not rely on memory alone.

Operation	Typical trigger	Reference
INIT	No wiki yet; user wants a new knowledge base	references/init.md
INGEST	New or changed files in raw/, pasted content, or URL to add	references/ingest.md
QUERY	Question that should be answered from wiki pages, not general knowledge	references/query.md
UPDATE	User wants edits, corrections, or merges on existing pages	references/update.md
LINT	“Lint”, health check, gaps, inconsistencies, optional raw vs files.log drift	references/lint.md

One message can imply several steps (e.g. INGEST then LINT). Order them sensibly—often INIT first if missing, then INGEST / UPDATE / QUERY, and LINT when checking health after substantive changes.

Routing hint

wiki/index.md + wiki/log.md present at wiki root?
├─ No → INIT → references/init.md
├─ Yes →
│   ├─ New/changed raw/, or paste/URL to capture? → INGEST → references/ingest.md
│   ├─ Domain question grounded in the wiki? → QUERY → references/query.md
│   ├─ "lint" / health check / find gaps? → LINT → references/lint.md
│   ├─ Revise or correct existing pages? → UPDATE → references/update.md
│   └─ Paste or URL only? → save under raw/, then INGEST → references/ingest.md

Wiki Structure

Authoritative layout is whatever lwiki structure prints. Run that command and treat the output as the single source of truth for INIT and whenever you need to understand the wiki structure; do not invent alternate directory trees or maintain a parallel diagram in prose.

At a glance: <wiki-root>/ has AGENTS.md (editable domain schema), CLAUDE.md (thin file that imports @AGENTS.md for Claude Code), assets/, raw/ (including auto-managed files.log), and wiki/ with index.md, log.md, overview.md, plus summaries/, concepts/, entities/, insights/.

Tooling (required)

All structural operations use the lwiki CLI. Never hand-edit files.log or create dirs manually.

Action	Command (wiki root as cwd unless noted)
Show canonical tree	lwiki structure
Bootstrap files + dirs	lwiki init <wiki-root> --domain "..." --sources "..."
Refresh raw/files.log	lwiki raw sync (or lwiki checkout)
Report drift (no write)	lwiki raw status

Page Conventions

Page templates are in templates/ — read the relevant template before creating a new page:

• templates/summary.md — source summaries
• templates/concept.md — concept pages
• templates/entity.md — entity pages
• templates/insight.md — insights (point-in-time snapshots, NOT cascade-updated)
• templates/index.md — index table format

Common rules:

• Every page carries frontmatter with at minimum title, type, description, and updated — description is the one-line summary used by index.md, search snippets, and previews, so populate it on create
• Use [[wikilinks]] with plain filenames — no paths (e.g., [[rag]] not [[concepts/rag]])
• Start every page with a 1-2 sentence summary in the body (frontmatter description is the structured form of the same idea)
• Every page ends with a ## See Also section for cross-references
• Insight pages add a ## Citations section for external sources (URLs, DOIs)
• Slugs: lowercase, hyphen-separated (e.g., attention-mechanism.md)
• Raw files: no date prefix in filename; dates tracked via frontmatter
• Forward references ([[not-yet-written]]) are tolerated — the backlink audit and cascade update will resolve them

Key Rules

1. LLM writes wiki; human curates sources and asks questions
2. raw/ is immutable — never modify
3. Log and index only on wiki/ file changes — no-op queries don't write anything
4. Ask only when uncertain — proceed autonomously; escalate when facts are ambiguous, sources conflict, or a change would alter meaning
5. Pages are not bound to raw files — LLM determines relevance across the entire wiki
6. Backlink audit on every ingest — scan all pages for missing links to new content
7. Insights are snapshots — not cascade-updated; add reverse links in See Also (Obsidian backlinks invisible to LLM)
8. Schema co-evolves — suggest AGENTS.md changes; user confirms; log records
9. Use lwiki CLI for INIT, structure, and raw/files.log — see Tooling

Tips for Users

Surface these to the user when relevant (e.g., during INIT, first ingest, or when they ask for help):

• Obsidian Web Clipper browser extension is the best way to capture web articles — bypasses anti-scraping etc.
• Use Obsidian's graph view to spot orphan pages and hub pages.
• Dataview plugin can query pages by frontmatter fields (type, tags, updated).
• From the second source onward, pay attention to cross-source connections.