What problem does it solve?
It solves the problem of turning scattered raw notes, papers, and images into a maintainable, query-ready Obsidian knowledge base without re-deriving answers from scratch every time.
Core Features & Use Cases
- Three-layer wiki design: preserves immutable raw sources, produces a compiled wiki layer, and uses a schema layer to govern structure and workflows.
- Provenance-first knowledge: enforces extracted vs inferred vs ambiguous claim marking so trust and citation remain clear.
- Operational governance: defines wiki organization, page templates, confidence/lifecycle fields, link formatting rules, and config resolution so the system can run reliably over time.
- Best-fit use cases: knowledge management strategy, starting a new wiki, deciding how to structure categories/projects, and guiding ongoing maintenance practices.
Quick Start
Use the llm-wiki skill to set up and explain a three-layer Obsidian wiki pattern based on your intended vault categories and how you want provenance and schema to work.