What problem does it solve? Raw notes, papers, and conversation logs are hard to query directly, and RAG re-derives answers on every query. This Skill establishes a compiled, LLM-maintained Obsidian wiki where knowledge is distilled once into cross-referenced markdown pages and kept current over time. ## Core Features & Use Cases - Three-Layer Architecture: Separates immutable raw sources, the LLM-maintained wiki of categorized markdown pages, and the schema that governs structure and workflows. - Structured Page Schema: Provides page and paper deep-dive templates with frontmatter for provenance markers, typed relationships, confidence scores, lifecycle states, and importance tiers. - Manifest and Index Conventions: Defines .manifest.json source-key contracts, index.md, and log.md so ingest, query, and lint operations stay auditable and incremental. - Use Case: A researcher collecting arXiv papers and articles uses this pattern to organize an Obsidian vault where each source updates concept, entity, and reference pages with traceable provenance instead of re-summarizing sources per question. ## Quick Start Ask the assistant to explain the LLM wiki pattern and help set up a new Obsidian knowledge base using the three-layer architecture.
