vault-research

Invoke vault-research with the report path, for example a file under .mz/research or .mz/reports. The skill parses the report into sections, filters noise, proposes atomic notes for your approval, then writes them to your vault's permanent folder under a research/ subfolder.

Reports are split at H2 headings, then partitioned into sequential windows of at most 450 words, splitting oversize sections at sentence boundaries. Each window is dispatched separately to the atomization-proposer agent, which has a 500-word input cap.

Yes. A default noise list (Vote Tally, Methodology, Panel Perspectives, and similar) is applied, but the Phase 1.5 approval gate shows the full classification verbatim. You can reply with feedback to add or remove sections before any atomization begins.

Do not use it for raw multimodal captures like voice memos, images, PDFs, or YouTube links (use vault-ingest), for processing existing fleeting notes (use process-notes), or for proposing links between notes that already exist (use vault-connect).

The skill caps output at 15 notes per report. If merged proposals exceed the cap, near-duplicate titles are deduped first, then remaining proposals are truncated with a visible warning listing the dropped titles.

No. Three approval gates require explicit approval: noise exclusion, atomization proposals, and link suggestions. No vault writes occur until the proposals gate is approved, and rejecting the links gate leaves written notes untouched without a Related section.