New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Slm Bot Memory

by qualixar in qualixar/superlocalmemory

Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine).

AGPL-3.0Auto-check passedAgent Workflows

Install Slm Bot Memory

skills CLI
$ npx skills add qualixar/superlocalmemory --skill slm-bot-memory -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install qualixar/superlocalmemory slm-bot-memory --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/qualixar/superlocalmemory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/slm-bot-memory .claude/skills/slm-bot-memory && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
slm-bot-memory
GitHub stars
230
Token cost
~1.8k tokens
SKILL.md length
921 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine).

  • Works in 3 steps: agent_id (SLM_AGENT_ID env, or the… → SLM_DATA_DIR — the real isolation… → scope (see slm-scope) — inside a store…
  • Agent Workflows work in your project
  • SKILL.md covers Three things that sound like…, Namespacing that actually works, What never goes into memory,… and Checklist for a new bot on an…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Slm Bot Memory is an agent skill from qualixar/superlocalmemory. Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agentid attribution vs. profile/scope access, how to namespace by agentid + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new Grok-Bot-style host.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Open-source governed, local-first memory control plane for AI agents and teams. arXiv:2608.08253. The licence is AGPL-3.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/slm-bot-memory”

Requirements

  • Pre-approved tools (allowed-tools): remember, recall, search, session_init, switch_profile

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. agent_id (SLM_AGENT_ID env, or the agent_id parameter on
  2. SLM_DATA_DIR — the real isolation boundary. One store per bot that
  3. scope (see slm-scope) — inside a store two or more bots

What it can do on your machine

Read from SKILL.md and the folder at commit 26f8c68. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • remember
    • recall
    • search
    • session_init
    • switch_profile

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Slm Bot Memory loads about 1.8k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 921 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qualixar/superlocalmemory at commit 26f8c68, republished under its AGPL-3.0 licence (© qualixar). 921 words, ~1,807 tokens.

Download SKILL.mdSave it as .claude/skills/slm-bot-memory/SKILL.md (or your agent's skills folder).
name
slm-bot-memory
description
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.
allowed-tools
remember, recall, search, session_init, switch_profile
when_to_use
- First session on a Grok Bot computer or any shared-bot host - "Will my other bots see this memory?" - "How do I keep this bot's notes separate from that…

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

SettingWhat it controlsDoes it hide memories from another bot?
SLM_AGENT_IDAttribution — who gets credit for a memory in logs and summariesNo. 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 opensYes. 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 storeOnly the way you set it. personal (the default) stays within the writing profile; shared/global are explicit, user-initiated opt-ins.

A memory profile (the namespace profile_id and switch_profile select) is not a fourth kind of isolation between bots. Any local caller that can name a profile can read it, and switch_profile moves the active profile for every bot on the computer. Treat profiles as organisation, not privacy.

The practical rule: SLM_AGENT_ID tells you who wrote something; SLM_DATA_DIR and scope decide who can read it. If two bots on the same Grok Bot computer use the same SLM_DATA_DIR (the common case — it is a shared filesystem, and nothing in Grok Bot's plugin model points different bots at different data directories by default), they see each other's personal-scope memories too, the same way two terminal sessions on one laptop would. Giving two bots different SLM_AGENT_ID values does not change that — it only changes whose name shows up on the memory.

If you need one bot's memories genuinely unreachable from another, that bot needs its own SLM_DATA_DIR (or a store where company mode with roles is configured — see slm-governance), not just its own SLM_AGENT_ID or its own profile.

Namespacing that actually works

Use all three dimensions together, each for what it is good at:

  1. agent_id (SLM_AGENT_ID env, or the agent_id parameter on remember/recall directly) — so a human or another agent reading get_memory_summary or the stored facts later can tell which bot said what. Set it to something stable and specific: grok_bot_support, grok_bot_release_notes, not a generic bot.
  2. SLM_DATA_DIR — the real isolation boundary. One store per bot that genuinely needs privacy from the others. A profile_id inside a shared store groups memories but does not hide them.
  3. scope (see slm-scope) — inside a store two or more bots legitimately share, keep writes personal by default and only promote to shared/global when a fact is meant for every bot on that store.
remember(
  content="Deploy window for the support bot is Tue/Thu 14:00-16:00 UTC",
  tags="ops,schedule",
  agent_id="grok_bot_support",
  session_id="<sid>",
)
recall(
  query="deploy window",
  agent_id="grok_bot_support",
  session_id="<sid>",
)

Recall is not filtered by agent_id automatically — it is attribution on the written record. If you need "only what this bot wrote", pass saved_by="grok_bot_support" to recall (or --saved-by on slm recall), which keeps only memories saved by that agent id. It filters; it does not protect, because another bot can leave it out.

Show full SKILL.md (353 more words)Show less

What never goes into memory, on any host

This is not Grok-Bot-specific — it is the baseline for every SLM host — but it matters more here because a shared computer means a shared blast radius if it is violated:

  • Secrets, API keys, tokens, passwords, certificates. Never pass them to remember, even "just this once" or "temporarily." If a fact needs to reference that a credential exists, store the fact of its existence and where to rotate it, never the value.
  • Personal data about identifiable people that was not already something the user explicitly asked to be remembered about themselves (names, emails, addresses, health, financial details of third parties).
  • Anything from Grok Bot's shared filesystem you did not write yourself and were not asked to remember. "Files are visible to every Bot" on that computer (Grok Bot's own docs) — a file being readable is not the same as having permission to copy its contents into long-term memory that other bots and later sessions will see.
  • Command-line credentials. Grok Bot's own docs note these are shared across bots on the computer; SLM must not become a second, more durable copy of them.

If you are unsure whether something is a secret, treat it as one and ask the user before storing anything derived from it.

Checklist for a new bot on an existing shared host

  1. Confirm SLM_DATA_DIR — is this bot meant to share the existing store, or does it need its own? (slm status --json on the computer shows data.base_dir and data.db_path.)
  2. Set a specific SLM_AGENT_ID for this bot before the first remember.
  3. Read slm-scope before writing anything with scope="shared" or scope="global" — those are machine-wide, not just cross-bot.
  4. Read the "never goes into memory" list above once, out loud if you are unsure, before the first write on this host.
  • slm-getting-started-bot — first-session setup for a headless bot host
  • slm-scope — the personal/shared/global visibility model this skill namespaces on top of
  • slm-profile — memory profiles versus tool sets, and what switching does
  • slm-governance — role-based access when a store has multiple human/bot members and real access control, not just convention

SuperLocalMemory v4.1.24 · Qualixar · AGPL-3.0-or-later

© qualixar, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugin/skills/slm-bot-memory of qualixar/superlocalmemory.

Open the folder on GitHubat commit 26f8c68

Compare with similar skills

Slm Bot Memory next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Slm Bot Memory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slm Bot Memory this skillqualixar/superlocalmemory230—~1.8kAutomated safety check: PassAGPL-3.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from qualixar/superlocalmemory

All 17 skills in this repo

  • Superlocalmemory

    qualixar/superlocalmemory

    AI agent memory with mathematical foundations. An agent skill from qualixar/superlocalmemory.

    230 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Slm Graph

    qualixar/superlocalmemory

    Index and query a codebase as a structural graph — build the code graph, trace blast radius of a change, find callers/callees/inheritors, semantic code search by meaning, assemble PR review context…

    230 GitHub stars~3k tokensUpdated today
    Auto-check: notes

  • Slm Loop

    qualixar/superlocalmemory

    Gate-verified bounded loops with SuperLocalMemory as the durable ledger.

    230 GitHub stars~2k tokensUpdated today
    Auto-check: notes

  • Slm Recall

    qualixar/superlocalmemory

    Search and retrieve facts, decisions, and past context from SuperLocalMemory.

    230 GitHub stars~5.1k tokensUpdated today
    Auto-check: notes

  • Slm Remember

    qualixar/superlocalmemory

    Capture durable facts, decisions, constraints, and gotchas into SuperLocalMemory.

    230 GitHub stars~3.8k tokensUpdated today
    Auto-check: notes

  • Slm Scope

    qualixar/superlocalmemory

    Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine).

    230 GitHub stars~1.6k tokensUpdated today
    Auto-check: notes

Categories

Questions about Slm Bot Memory

What does Slm Bot Memory do?

Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Slm Bot Memory is an agent skill from qualixar/superlocalmemory. Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine).

When should I use Slm Bot Memory?

Slm Bot Memory fits situations like: agent Workflows work in your project.

How do I install Slm Bot Memory in Claude Code?

Run `npx skills add qualixar/superlocalmemory --skill slm-bot-memory -a claude-code`. Or copy the skill folder (plugin/skills/slm-bot-memory in qualixar/superlocalmemory) into .claude/skills/slm-bot-memory in your project. Claude Code loads it when a task matches its description.

How do I install Slm Bot Memory in Codex?

Run `npx skills add qualixar/superlocalmemory --skill slm-bot-memory -a codex`. Or copy the skill folder (plugin/skills/slm-bot-memory in qualixar/superlocalmemory) into .agents/skills/slm-bot-memory in your project. Codex loads it when a task matches its description.

Can I use Slm Bot Memory in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qualixar/superlocalmemory --skill slm-bot-memory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slm-bot-memory, .gemini/skills/slm-bot-memory, .github/skills/slm-bot-memory and .opencode/skills/slm-bot-memory in your project.

What does Slm Bot Memory need to run?

SKILL.md names no scripts, command-line tools or credentials: Slm Bot Memory is instructions for the agent only. Its frontmatter pre-approves these tools: remember, recall, search, session_init, switch_profile.

Does Slm Bot Memory access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Slm Bot Memory safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Slm Bot Memory use?

Slm Bot Memory is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slm Bot Memory use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Slm Bot Memory?

Skills that share tags, products or a category with Slm Bot Memory: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slm Bot Memory?

qualixar (a GitHub organization) maintains it in qualixar/superlocalmemory, which has 230 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 10, 2026.

Source: qualixar/superlocalmemory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.