Slm Bot Memory
Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agent_id attribution vs. profile/scope access, how to namespace by agent_id + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new Grok-Bot-style host.
Install
/plugin marketplace add qualixar/superlocalmemoryThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add qualixar/superlocalmemory --skill slm-bot-memorygit clone --depth 1 https://github.com/qualixar/superlocalmemory.git /tmp/superlocalmemory
mkdir -p ~/.claude/skills
cp -r /tmp/superlocalmemory/antigravity-plugin/skills/slm-bot-memory ~/.claude/skills/slm-bot-memoryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# slm-bot-memory — Cross-Bot Memory on a Shared Host SuperLocalMemory ships as an MCP server. On a single-user laptop, one bot is the only thing talking to it. On a **shared-bot host** — Grok Bot's "one computer, shared by all your Bots" model, several Cursor windows, or any setup where more than one agent process points at the same install — several agents can reach the same memory store at once. This skill is about that case: what is actually isolated, what is not, and what must never be written regardless. --- ## Three things that sound like isolation and are not the same | Setting | What it controls | Does it hide memories from another bot? | |---|---|---| | `SLM_AGENT_ID` | **Attribution** — who gets credit for a memory in logs and summaries | **No.** It is metadata, never an authenticated principal (verified in `mcp/agent_context.py`'s own docstring). Any bot that can query the same store can read a memory written under a different `agent_id`. | | `SLM_DATA_DIR` (profile root) | **Which database file** the daemon opens | **Yes.** Two bots pointed at different `SLM_DATA_DIR` values have fully separate, independent memory stores — nothing is shared unless you explicitly configure sharing. | | `scope` (`personal` / `shared` / `global`, see `slm-scope`) | **Visibility inside one store**, between profiles that share that store | Only the way you set it. `personal` (the default) stays within the writing profile; `shared`/`global` are explicit, user-initiated opt-ins. |
Details
- Skill name
slm-bot-memory- Repository
- qualixar/superlocalmemory
- Path
antigravity-plugin/skills/slm-bot-memory/SKILL.md- License
- AGPL-3.0
- Repo updated
- 18 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Slm Bot Memory skill do?
Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agent_id attribution vs. profile/scope access, how to namespace by agent_id + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new Grok-Bot-style host.
How do I install the Slm Bot Memory skill?
Claude Code plugin: /plugin marketplace add qualixar/superlocalmemory. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Slm Bot Memory popular?
It lives in qualixar/superlocalmemory, which has 278 GitHub stars and 36 forks, and is included in 1 curated skill list.
Related skills
Slm Cache
278qualixar/superlocalmemory
KV cache for repeated reads — call slm_cache_get(key) first; on a miss do the expensive operation then slm_cache_set(key, value, ttl_seconds) to store it; on a hit use the returned value directly; always fail-open (hit:false on any error, never raises); saves tokens when the same file, query result, or tool output is read more than once in a session.
Slm Compress
278qualixar/superlocalmemory
Compress large text, tool output, or transcripts to reduce context-window usage while keeping the full 1M window intact — call slm_compress(content, mode, reversible, ttl_seconds) to shrink content; if the result is lossy a ccr_id is returned so you can call slm_retrieve(ccr_id) later to recover the exact original; always fail-open (ok:false → continue with the original).
Slm Getting Started Bot
278qualixar/superlocalmemory
First-session orientation for SuperLocalMemory on a headless bot host (Grok Bot, or any Cursor-format plugin install with no hooks, no dashboard, and no interactive setup wizard). What is different here vs. Claude Code/Codex, which 19 tools are actually available, and the first three calls to make.
Slm Loop
278qualixar/superlocalmemory
Gate-verified bounded loops with SuperLocalMemory as the durable ledger. Use when a task has a checkable acceptance condition and you must iterate until an INDEPENDENT gate passes — never stopping because the agent believes it is done. `slm_loop_run` (MCP) waits, under hard bounds, for an independently executed check registered by the operator to pass; `slm loop demo` shows the control flow keyless; `slm loop history` and `slm loop show <run_id>` (or `slm_loop_history` / `slm_loop_show`) inspect past runs, whose every lap is stored as queryable SLM memory (tag `loop:<name>`). Terminal statuses
21 Day Self Interview
108Forlives/21-day-self-interview
夜间自我访谈引导(21 天)。扮演资深存在主义心理咨询师,每晚提三个有意义的问题,记录回答并在节点回映,帮助用户看清自己。Use when running a nightly self-inquiry / journaling ritual driven by a scheduled task.
Slm Profile
278qualixar/superlocalmemory
Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switch_profile or slm profile switch to change the active memory profile, the profile_id argument to read or write another profile for one call, and `slm tools set <name>` to choose the tool set every connected app sees. Required when working across multiple projects, clients, or tenants.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.