vault-memorylisted
Install: claude install-skill yusufkaran/karpathy-llm-wiki-autopilot
# Vault memory
The user's persistent memory is an Obsidian vault, kept in sync across machines with git.
- Tool: `~/.vault-memory/bin/vm` (called `vm` below). If it does not exist, the system is not installed: go to **Setup**.
- Vault path: the `vault` field in `~/.vault-memory/config.json`.
- Rules: `CLAUDE.md` in the vault root. Read it before writing anything to the vault. If it conflicts with this skill, `CLAUDE.md` wins.
A background worker processes sessions on its own about 20 minutes after they go idle. Use this skill when the user doesn't want to wait, asks something from memory, or wants to install or change the system.
## Which operation
| The user says | Section |
|---|---|
| "Save this session", "put this in my vault" | Process this session now |
| "Remember this: …", a specific piece of content | Write a specific note |
| "Where did we leave off", "what did we do in X" | Answer from memory |
| "How much did I work", "what did I do last week" | Time report |
| "Open my dashboard" | Dashboard |
| "Process this article / PDF" | Process a source |
| "Check the vault", "lint" | Health check |
| "My memory isn't updating" | Troubleshooting |
| "Set up vault memory", "add this machine", "upgrade", "remove it" | Setup, Upgrade, Uninstall |
## Process this session now
1. Find the session id. The `<vault-memory>` block added to the context at session start has a "Session id" line.
2. Run the worker for this session. It can take a minute or two; use a timeout of at