Slm Profile

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.

278 stars 36 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add qualixar/superlocalmemory

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add qualixar/superlocalmemory --skill slm-profile
Manual install
git clone --depth 1 https://github.com/qualixar/superlocalmemory.git /tmp/superlocalmemory
mkdir -p ~/.claude/skills
cp -r /tmp/superlocalmemory/antigravity-plugin/skills/slm-profile ~/.claude/skills/slm-profile

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# slm-profile — Memory Profiles and Tool Sets

Two different things are called "profile" in SuperLocalMemory. Keep them apart.

- A **memory profile** is a namespace inside one store. It has its own memories,
  knowledge graph, learned patterns, retention settings and audit trail. A fresh
  install has one, called `default`. This is what `switch_profile`,
  `slm profile` and the `profile_id` argument are about.
- An **MCP tool set** (`SLM_MCP_PROFILE`: `core`, `code`, `full`, `power`,
  `mesh`) decides which tools the server shows your host. `switch_profile` does
  not change it.

A memory profile organises memory. It is not a security boundary: any local
caller that can name a profile can read it, unless the user has turned on company
mode with roles. For memories that must be unreachable from another bot or user,
use a separate data directory (`SLM_DATA_DIR`) or company mode (`slm-governance`).

---

## Memory profiles

```bash
slm profile list [--json]
slm profile create <name> [--json]
slm profile switch <name> [--json]
slm status --json          # data.profile is the active profile
```

Creating a profile is a CLI action; there is no MCP tool for it. Over MCP:

```
switch_profile(
  profile_id: str,   # the name of an existing profile
)
```

`switch_profile` changes the **active profile**. The change is not private to
your session: it is written as the machine's active profile, so every later call
Read the full skill on GitHub

Details

Skill name
slm-profile
Path
antigravity-plugin/skills/slm-profile/SKILL.md
License
AGPL-3.0
Repo updated
18 November 2026

FAQ

What does the Slm Profile skill do?

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.

How do I install the Slm Profile 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 Profile 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 Bot Memory

278

qualixar/superlocalmemory

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.

Productivity & NotesIn 1 list36

Slm Cache

278

qualixar/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.

OtherIn 1 list36

Slm Compress

278

qualixar/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).

Writing & ContentIn 1 list36

Slm Remember

278

qualixar/superlocalmemory

Capture durable facts, decisions, constraints, and gotchas into SuperLocalMemory. Use when the user says "remember that", "save this decision", "note this constraint", or when a session produces a conclusion worth persisting across sessions. Always recall first to avoid duplicates.

Productivity & NotesIn 1 list36

Slm Loop

278

qualixar/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

Productivity & NotesIn 1 list36

Slm Scope

278

qualixar/superlocalmemory

Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine). Default is always personal. Only change scope when the user explicitly asks to share a memory across workspaces. Works with both remember (write scope) and recall (read scope flags).

Productivity & NotesIn 1 list36

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.