How claude-mem works (memory plugin explainer)
Explains the claude-mem plugin — how observations are captured, when memory injection kicks in, where data lives
- What
- Explains the claude-mem plugin — how observations are captured, when memory injection kicks in, where data lives
- Cost
- Free
- Needs
- nothing for this explainer — to get the memory capability itself, install the claude-mem plugin separately (memory is local to one machine)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @thedotmack's explainer skill for the claude-mem plugin: how every Read/Edit/Bash becomes a compressed observation, how observations get summarized at session end, when memory injection starts (second session in a project — the first seeds memory), where everything lives (`~/.claude-mem`, SQLite + vector index, machine-local), and the privacy boundary (nothing leaves the machine except calls to the AI provider configured for compression; local installs contact cmem.ai once at signup). By @thedotmack, listed here with credit to its creator. Honest caveats: this is an explainer doc for the claude-mem plugin — install the actual claude-mem plugin to get the memory capability itself; memory is local to one machine, not synced. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing for this explainer — to get the memory capability itself, install the claude-mem plugin separately (memory is local to one machine) Install "How claude-mem works (memory plugin explainer)" for me. It gives the agent @thedotmack's explanation of the claude-mem plugin: how observations are captured from Read/Edit/Bash, summarized at session end, auto-injected into future sessions, where data lives (~/.claude-mem, machine-local), and the privacy boundary — useful when the user asks "how does claude-mem work?". Apache-2.0 licensed. Repository: https://github.com/thedotmack/claude-mem/blob/main/plugin/skills/how-it-works/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "how-it-works". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing for the explainer — install the claude-mem plugin itself if you want the memory capability). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.