What problem does it solve? Turning scattered notes in an Obsidian vault into a coherent, trustworthy narrative is slow and error-prone. This Skill compiles vault evidence on a topic into a structured Markdown readout where every factual sentence carries an adjacent citation, so nothing relies on model memory or outside knowledge. ## Core Features & Use Cases - Three voice modes: Produce an executive briefing, a plain-language explanation, or a progressive lecture, each with a fixed section skeleton defined in references/voices.md. - Claim ledger and citation audit: Drafts a ledger of claims marked as supported, inferred, or ambiguous before writing prose, and renders citations as wikilinks or Markdown links per the vault's OBSIDIAN_LINK_FORMAT. - Filtered retrieval and safe failure: Honors visibility filters like "public only", excludes internal/PII-tagged pages, falls back from QMD to ripgrep search, and never invents content to fill evidence gaps. - Optional persistence and logging: With --save, writes the readout to _readouts/ with frontmatter, appends a WIKI_NARRATE event to log.md, and refreshes hot.md only after a successful save. - Use Case: Ask for a briefing on a project topic and receive a Markdown document where each claim links back to the exact vault pages that support it, with a Coverage footer listing sources and known gaps. ## Quick Start Ask the assistant to run /wiki-narrate on a topic from your Obsidian vault, optionally choosing a voice such as briefing, plain-language, or lecturer and adding --save to persist the readout.
