vault-answer

Invoke the skill with your question, for example "what does my vault say about X". It searches vault notes, reads up to 20 of them, and returns an answer where every factual claim carries an inline [[wikilink]] citation plus a Sources list.

It resolves the vault path from the OBSIDIAN_VAULT_PATH environment variable first, then MZ_VAULT_PATH, then walks up from the working directory looking for a .obsidian folder. If none resolve, it asks you directly.

No. The skill is strictly read-only on the vault. It only writes artifacts like answer.md and state.md inside a .mz/task/<task_name>/ directory, never touching vault files.

The answer always includes an ## Unknowns section listing aspects the vault could not support. A thin vault produces a longer Unknowns list rather than fabricated content from general knowledge.

The check requires at least one [[wikilink]] per 50 words of answer prose (ratio 0.02) to keep every claim auditable. If the first attempt falls short, the agent retries once; persistent shortfalls are flagged as a concern in state.

Do not use it for editing notes, finding links between notes (use vault-connect), frontmatter or schema questions (use vault-schema), or general questions unrelated to vault content, which can be answered directly.