llm-wiki

To compile scattered research notes into a linked Obsidian wiki, the skill incrementally ingests source documents into an immutable raw folder and generates interlinked markdown pages with wikilinks and frontmatter summaries.

Maintaining an Obsidian knowledge base without per-query retrieval involves using a compile-first pipeline that builds a persistent wiki state, deriving answers from interlinked entity pages instead of fragmented search queries.

Wikilinking for entities in a personal knowledge management wiki works by converting named entities and concepts extracted from source documents into navigable [[Wikilink]] references within the generated markdown files.

Yes, you can audit your Obsidian vault for broken links and hallucinated claims using an on-demand lint flow that scans the compiled wiki state to detect orphans, contradictions, and broken references via an append-only log.

Yes, this research workflow requires a strict folder structure separating immutable inputs in a raw directory from compiled markdown in a wiki directory, alongside a schema file for consistent page generation.

A compile-first wiki approach replaces standard RAG for research notes by maintaining a continuously updated, interlinked knowledge state, avoiding the fragile retrieval and one-off answers associated with per-query lookups.