Run one Vault grooming pass (preview first, guarded apply on request) to consolidate stale, oversized, or duplicated notes. Use for periodic memory maintenance or when the user says the vault needs cleaning.
Installs into .claude/skills of the current project.
Are you the author of Vault Groom?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/matteopasseri407-vault-groom)
---
name: vault-groom
description: Run one Vault grooming pass (preview first, guarded apply on request) to consolidate stale, oversized, or duplicated notes. Use for periodic memory maintenance or when the user says the vault needs cleaning.
---
# Groom the vault
Any text after the command is the request, not an argument: a focus area or
note to prioritize is context for you, and the command itself takes only a
mode, `preview` (the default) or `apply`. Any other word is refused with
exit 2.
1. Start read-only, always: run `vault-groom` (bare = preview). It
proposes one grooming tranche and writes nothing into the vault -- a
bare invocation can never modify it (the only file it writes is its own
log in the system temp directory).
2. Explain the proposed tranche in plain language: which notes it would
compress, merge, or archive, or whose frontmatter or links it would
fix, and why. Deletion is not one of its actions: in doubt it archives.
Flag anything that looks risky (recovery notes, recent material) before
the user decides.
3. Only if the user explicitly asks to proceed, run `vault-groom apply`.
Its own guardrails stay in charge: it re-shows the tranche, requires a
typed "yes", executes in a throwaway clone with no remote, audits the
result, and only then promotes it into the real vault. Never work
around any of that, and never edit vault notes by hand to "help" the
groomer.
4. Report what actually changed (or that nothing did), and whether a
follow-up pass looks worthwhile.
