Save one durable fact to the KnowledgeVault with the hygiene decision rule applied. Use when the user asks to remember, save, or note something for the future.
Installs into .claude/skills of the current project.
Are you the author of Vault Save?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/matteopasseri407-vault-save)
---
name: vault-save
description: Save one durable fact to the KnowledgeVault with the hygiene decision rule applied. Use when the user asks to remember, save, or note something for the future.
---
# Save a durable fact
The text after the command is the fact to save.
1. Apply the decision rule first: will this still matter in weeks or
months? Will a future session reuse it to decide, restore, or avoid
repeating work? Is it non-sensitive and safe to sync? If any answer is
no, tell the user why it does not belong in the Vault and stop.
2. Find the canonical home: search the vault (`search_notes` or
`semantic_search`) for a note that already covers the topic. Prefer
updating that note over creating a new one.
3. Write through the `vault-library` MCP (`append_note`; `update_section`
with its per-section hash when the fact belongs to one existing section;
`update_note` with `expected_hash` for whole-note rewrites). Only
`create_note` for a genuinely new stable topic, and then add an inbound
pointer in `00-START-HERE.md`. In Local-Only mode (no remote, no MCP)
there is no `vault-library` to write through: edit the Markdown note
directly and commit it with plain `git` instead — that is the correct
and only path there, not a fallback (`03-INFRA/vault-write-architecture.md`).
4. Confirm the write landed and report exactly where the fact now lives
(note path plus the line or section).
Never store secrets, tokens, or credential-adjacent material; keep the
entry short (a fact, not a diary).
