Agent skill

Slm Scope

by qualixar in qualixar/superlocalmemory

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

AGPL-3.0Auto-check: notesAgent Workflows

Install Slm Scope

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

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

GitHub CLI
$ gh skill install qualixar/superlocalmemory slm-scope --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-scope .claude/skills/slm-scope && 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-scope
GitHub stars
227
Token cost
~1.4k tokens
SKILL.md length
465 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
AGPL-3.0

At a glance

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

  • Explicitly asks to share a memory across workspaces
  • SKILL.md covers The Three Scopes, Opt-in is mandatory, Writing a shared or global fact and Reading shared or global facts, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Slm Scope is an agent skill from 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).

Its SKILL.md is about 1.4k 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. It works with Model Context Protocol. 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

  • Explicitly asks to share a memory across workspaces

Example prompts

  • “Use the slm-scope skill to control memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all…”
  • “/slm-scope”

Requirements

  • Pre-approved tools (allowed-tools): remember, recall, search, list_recent, Bash

What it can do on your machine

Read from SKILL.md and the folder at commit ce2d7a9. 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
    • list_recent
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).

    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 Scope loads about 1.4k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 465 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: remember, recall, search, list_recent, Bash

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 ce2d7a9, republished under its AGPL-3.0 licence (© qualixar). 465 words, ~1,395 tokens.

Download SKILL.mdSave it as .claude/skills/slm-scope/SKILL.md (or your agent's skills folder).
name
slm-scope
description
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).
allowed-tools
remember, recall, search, list_recent, Bash
when_to_use
- "Share this memory with the team profile" - "Store this globally so all my agents can see it" - "Recall anything shared from the work profile" - "Can other…

slm-scope — Memory Scope and Sharing Model

SuperLocalMemory is profile-isolated by default. Every profile is a fully independent memory namespace. The scope model adds controlled, opt-in sharing between profiles on the same machine — it is never active unless you explicitly set it.


The Three Scopes

ScopeVisibilityWhen to use
personalActive profile onlyDefault — all facts. Never set explicitly.
sharedActive profile + shared_with profilesTeam handoffs, shared project context
globalEvery profile on this machineMachine-wide conventions, org-wide rules

The default is always personal. A fact stored without a scope argument is private to the profile that stored it. Recall without scope flags returns only personal facts. This is identical to single-profile SLM.


Opt-in is mandatory

Never set scope="shared" or scope="global" (or the recall equivalents include_shared, include_global) unless the user explicitly asks you to share or read across profiles. This is a hard rule — scope expansion is an action with team-wide or machine-wide impact, and it must always be user-initiated.


Writing a shared or global fact

share with specific profiles
remember(
  content="API gateway rate limit is 1000 req/min per client",
  tags="api,limits,ops",
  project="platform",
  importance=8,
  session_id="<sid>",
  scope="shared",
  shared_with="devops-profile,backend-profile",
)

shared_with is a comma-separated list of profile IDs that should be able to recall this fact. Use slm status to see the current profile name — that is the profile_id to supply.

share with all profiles on the machine
remember(
  content="All services must enforce TLS 1.3 minimum",
  tags="security,tls,global",
  project="infra",
  importance=9,
  session_id="<sid>",
  scope="global",
)

scope="global" makes the fact visible to every profile on this machine. Use this only for machine-wide conventions (security rules, org-wide constraints).


Reading shared or global facts

By default, recall returns only the active profile's personal facts. To surface shared and global facts, pass the opt-in flags:

recall(
  query="rate limiting rules",
  limit=20,
  include_global=True,   # include global-scope facts
  include_shared=True,   # include facts shared with this profile
  session_id="<sid>",
)

You can opt in to either or both flags independently. Only the active profile's permitted shared facts are returned — you cannot read another profile's personal facts.

Show full SKILL.md (185 more words)Show less
CLI equivalents
bash
# Recall with global facts included
slm recall "rate limiting rules" --include-global

# Recall with shared facts included
slm recall "rate limiting rules" --include-shared

# Both
slm recall "rate limiting rules" --include-global --include-shared

# Store a global fact
slm remember "TLS 1.3 minimum" --scope global

# Store a shared fact (shared-with is a comma-separated list of profile IDs)
slm remember "API rate limit 1000/min" --scope shared --shared-with devops,backend

CLI flags verified in source: --include-global / --no-global, --include-shared / --no-shared, --scope personal|shared|global, --shared-with <profile-ids>.


Configuring scope defaults

Per-profile defaults live in mode_a/b/c.json configuration. To make a profile always include global facts without passing flags each time:

json
{
  "recall": {
    "include_global": true,
    "include_shared": false
  }
}

Changing the default requires editing the profile config directly — this is an admin-level operation.


Enterprise governance

In a governed workspace (admin/member/viewer roles), scope expansion may be restricted:

  • Viewers cannot write scope="global" facts — their writes are always personal.
  • Members can write scope="shared" with profiles in their access list.
  • Admins can write scope="global" unrestricted.

See slm-governance for the full enterprise behavior model.


Scope deletion and retention

A scope="global" fact deleted by one profile is deleted for all profiles. A scope="shared" fact is deleted from all profiles that had access to it. Use slm forget "<query>" --dry-run before any deletion involving shared facts to review the impact. See slm-remember for the full deletion discipline.


  • slm-remember — full fact storage reference including scope parameters
  • slm-recall — full retrieval reference including include_global/include_shared
  • slm-profile — what a profile is and how to switch between them
  • slm-governance — enterprise role restrictions on scope

SuperLocalMemory v4.1.21 · 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-scope of qualixar/superlocalmemory.

Open the folder on GitHubat commit ce2d7a9

Compare with similar skills

Slm Scope 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 Scope compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slm Scope this skillqualixar/superlocalmemory227—~1.4kAutomated safety check: NotesAGPL-3.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Fastmcp Client CLIPrefectHQ/fastmcp28k1 repos~823Automated safety check: PassApache-2.0
MemPalace Memory SearchMemPalace/mempalace59k—~1.4kAutomated safety check: PassMIT

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 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed
  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from qualixar/superlocalmemory

All 13 skills in this repo
  • Superlocalmemory

    qualixar/superlocalmemory

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

    227 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…

    227 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes
  • Slm Loop

    qualixar/superlocalmemory

    Run gate-verified bounded loops with SuperLocalMemory as the durable ledger.

    227 GitHub stars~1.2k tokensUpdated today
    Auto-check: notes
  • Slm Recall

    qualixar/superlocalmemory

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

    227 GitHub stars~3.3k tokensUpdated today
    Auto-check: notes
  • Slm Remember

    qualixar/superlocalmemory

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

    227 GitHub stars~2.3k tokensUpdated today
    Auto-check: notes
  • Slm Status

    qualixar/superlocalmemory

    Health and optimization stats for SuperLocalMemory — call slmoptimizestats() for live compression and cache counters (compressruns, tokenssavedcompress, cacheproxyhits, cacheproxymisses…

    227 GitHub stars~1.7k tokensUpdated today
    Auto-check: notes

Categories

Questions about Slm Scope

What does Slm Scope do?

Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine). Slm Scope is an agent skill from qualixar/superlocalmemory. Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine).

When should I use Slm Scope?

Slm Scope fits situations like: explicitly asks to share a memory across workspaces.

How do I install Slm Scope in Claude Code?

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

How do I install Slm Scope in Codex?

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

Can I use Slm Scope 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-scope -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-scope, .gemini/skills/slm-scope, .github/skills/slm-scope and .opencode/skills/slm-scope in your project.

What does Slm Scope need to run?

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

Does Slm Scope 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 Scope safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Slm Scope use?

Slm Scope 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 Scope use?

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Scope?

Skills that share tags, products or a category with Slm Scope: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slm Scope?

qualixar (a GitHub organization) maintains it in qualixar/superlocalmemory, which has 227 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 8, 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.