llm-wikilisted

# LLM Wiki Use this skill when the user wants a persistent knowledge base that compounds over time instead of answering from raw documents from scratch on every turn. ## Core Model Treat the wiki as three layers: - `raw/` is the immutable source collection. Read from it; do not edit or rewrite it during normal maintenance. - `wiki/` is the maintained knowledge layer. This is where summaries, entity pages, concept pages, and durable analyses live. - `AGENTS.md`, `index.md`, and `log.md` define and track the system: `AGENTS.md` is the schema and workflow contract, `index.md` is the catalog, and `log.md` is the append-only timeline. This is not a one-shot note dump. The goal is to integrate new information into existing pages, preserve cross-references, and keep the wiki internally coherent as the source set grows. ## Resolve The Wiki Root Use this order: 1. a user-specified wiki root 2. an already-structured repo or vault containing `raw/`, `wiki/`, `index.md`, and `log.md` 3. a confirmed markdown vault or notes repo chosen by the user 4. the current workspace only if the user explicitly wants the wiki here Do not assume the current workspace is the wiki root just because it contains Markdown files. If the target is an Obsidian vault, also follow `skills/obsidian/SKILL.md`. ## Orient Every Session When the user already has a wiki, always orient yourself before acting: 1. Read `AGENTS.md` first to understand the local schema, domain, taxonomy, link sty