save files the part of a conversation you choose as a note in your Obsidian vault. It never runs on its own and never archives a whole transcript. It looks for an existing note first, drafts the smallest useful note type, and shows the title, destination and changed paths before applying.
One transaction writes the note together with the index entry, a new log entry and a refreshed hot cache, so the vault stays navigable.
What You Get
- A new or updated note in the vault limited to the scope you selected
- An index entry, a top-of-file log entry and a hot cache under 500 words
- Source and claim ledger updates only when evidence changed
- A preview of title, destination and create or replace modes
- An operation ID and exact changed paths after apply
Common Use Cases
- Keeping a good answer from a research chat as a question note
- Recording a decision and its reasoning in the vault
- Saving a session summary you approved
What Makes It Unique
It saves on request only, in the scope selected, and uses the transaction engine so the note, index, log and hot cache land together or not at all. It asks before replacing an existing canonical note, supports a no-op when the content is already represented, and refuses to invent quotes or sources.
Under The Hood
The skill is instructions that point to the plugin’s transaction and provenance references. It needs no network access. It runs the plugin’s Python core script through the shell to inspect a workflow bundle and apply it with the approved plan hash, and that step is the only thing that writes to the vault. A Git checkpoint is a separate command run only when you ask. Host file write tools are not used for vault changes.