vaultr-memory
Extract and update personal memories from Vaultr notes into structured memory files. Use when the user wants to update their personal memory, extract memories from notes, run memory extraction, or refresh the personal memory base. Triggers on phrases like 'update my memory', 'extract memories from notes', 'run memory extraction', 'refresh personal memory', or any request to build or maintain a personal memory base from notes.
npx skills add skoowoo/vaultr-notes --skill vaultr-memory --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Vaultr Memory Extract Extracts personal memories from short notes (`/_shorts`) and the knowledge base (`/_knowledge`) into six structured memory files under `/_memory/`. On first run (no memory files exist yet), scans the last 90 days for a rich initial snapshot. On subsequent runs, scans only the last 2 days. Memories not reinforced over time gradually fade and are eventually removed. **Run all steps to completion without stopping or asking for confirmation.** Only speak at the final summary step. --- ## Inputs 1. **Self-introduction** — a brief description the user provides about themselves (name, role, projects, relationships, etc.). Used throughout extraction to identify personal content and disambiguate knowledge units. Ask for this if not provided. 2. **Extra scan paths** — additional vault path prefixes to scan beyond the two defaults (optional). 3. **Memory directory** — where memory files live (default: `/_memory/`). --- ## Step 1 — Determine run mode Check whether any memory file already exists: ```bash vaultr read /_memory/_identity.md ``` - **First run** (file not found): set `scan_window = 90` days. - **Incremental run** (file exists): set `scan_window = 2` days. Rec
- Inputs
- Step 1 — Determine run mode
- Step 2 — Collect content to process
- Step 3 — Extract evidence
- Source A: Short notes (/shorts)
- Source B: Knowledge base (/knowledge)
- Source C: Extra scan paths
- Step 4 — Update memory files
- File format
- Decay windows
- Update rules (apply in this order)
- Writing the file
- Step 5 — Summary
vaultr read /_memory/_identity.md vaultr short list --latest <scan_window> --limit 100 vaultr knowledge list --kind knowledge --latest <scan_window> --limit 50 vaultr knowledge read <path> vaultr create /_memory/_<dimension>.md --content "<content>" # new vaultr create /_memory/_<dimension>.md --content "<content>" --force # overwrite
What does the vaultr-memory skill do?
Extract and update personal memories from Vaultr notes into structured memory files. Use when the user wants to update their personal memory, extract memories from notes, run memory extraction, or refresh the personal memory base. Triggers on phrases like 'update my memory', 'extract memories from notes', 'run memory extraction', 'refresh personal memory', or any request to build or maintain a personal memory base from notes.
How do I install it?
Run `npx skills add skoowoo/vaultr-notes --skill vaultr-memory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From skoowoo/vaultr-notes, a repository with 74 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.