This shows you exactly what claude-mem is doing under the hood: capturing compressed observations from every Read, Edit, and Bash command, then auto-injecting relevant context into future sessions so you never re-explain your codebase. Memory kicks in on your second session in a project, and everything lives in ~/.claude-mem on your machine. The only network calls go to your configured AI provider for compression. It's the kind of explainer you'd want when a tool starts doing invisible things in the background and you need to know whether to trust it or rip it out.
npx skills add https://github.com/thedotmack/claude-mem --skill how-it-works