Slm Governance

Governed-workspace behavior for SuperLocalMemory. Covers roles (admin/member/viewer) and company mode, who administers a company-mode workspace (a signed-in admin, or `slm team` on the SLM computer), `slm token show` in strict mode, what remote web apps can never see or change, retention and lifecycle settings, the audit trail, GDPR export and erasure, and how agents must behave when operating under workspace governance. The audit and retention tools need the power MCP profile. Agents must never bypass governance controls.

278 stars 36 forksAI, LLMs & Agents 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-governance
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-governance ~/.claude/skills/slm-governance

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-governance — Governed Workspace Behavior

SuperLocalMemory can run with named users and roles per workspace (company
mode), keeps a compliance audit trail, applies a retention lifecycle, and ships
GDPR export and erasure commands. This skill documents how an agent must behave
in a governed workspace and what the governance tools really do. The MCP audit
and retention tools are in the `power` tool set, not the default: if they are
missing, tell the user to run `slm tools set power` and restart this app (see
`slm-profile`). The `slm gdpr` and `slm team` commands work either way.

---

## Role model

By default SLM is single-user: whoever runs it is the owner and nothing asks for
a login. Company mode adds named users, each with one role per workspace
(profile). A role in one workspace grants nothing in another.

| Role | Read | Write | Share (`shared`/`global` writes) | Delete | Manage users and settings |
|------|------|-------|-------|--------|-----------------|
| `viewer` | Yes | No | No | No | No |
| `member` | Yes | Yes | Yes | No | No |
| `admin` | Yes | Yes | Yes | Yes | Yes |

**Agent behavior by role:**

- **Viewer**: Only call `recall`, `search`, `fetch`, `list_recent` and other
  reads. Never call `remember`, `update_memory`, `delete_memory` or any write
  tool. If a write is refused, say so: "This workspace is read-only for my role."
- **Member**: May write memories, including `scope="shared"` and `scope="global"`
Read the full skill on GitHub

Details

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

FAQ

What does the Slm Governance skill do?

Governed-workspace behavior for SuperLocalMemory. Covers roles (admin/member/viewer) and company mode, who administers a company-mode workspace (a signed-in admin, or `slm team` on the SLM computer), `slm token show` in strict mode, what remote web apps can never see or change, retention and lifecycle settings, the audit trail, GDPR export and erasure, and how agents must behave when operating under workspace governance. The audit and retention tools need the power MCP profile. Agents must never bypass governance controls.

How do I install the Slm Governance 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 Governance 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 Mesh

278

qualixar/superlocalmemory

Cross-session peer coordination via the SLM mesh network. Lets multiple AI agent sessions on the same machine, and web apps the owner has allowed (ChatGPT, Claude on the web, Grok Bot, Muse, Composio), discover each other, send messages, wait for replies with mesh_wait, share lightweight state, and lock files to avoid conflicts. Covers the at-least-once delivery rule for web apps (pass ack_ids back as ack) and the two permissions a web app needs. Available in the default tool set and in the full, power and mesh MCP profiles. Only `slm mesh status` and `slm mesh peers` exist on the command line

AI, LLMs & AgentsIn 1 list36

Serve Model

213

modular/skills

Serve a model with MAX's `max serve` command: set up the environment (pixi or uv with the max-nightly conda channel / nightly wheel index), point the server at a Hugging Face repo or local checkpoint, target a custom architecture with `--custom-architectures`, and pick the right serve flags for the model. Use this whenever the user wants to run, launch, start, or host a model on MAX, bring up an OpenAI-compatible endpoint, serve a custom/ported architecture, debug a `max serve` startup failure, or figure out which serve flags (devices, quantization-encoding, max-length, task, trust-remote-code

AI, LLMs & Agents22

Slm Web Access

278

qualixar/superlocalmemory

Set up and troubleshoot SuperLocalMemory Web access, the optional link that lets web apps (ChatGPT, Claude on the web, Muse, Composio, other remote MCP clients) use the memory on this computer. Covers turning it on from the dashboard, adding and removing apps, read/save/session permissions, the second yes for bot messages and pictures (the Web access switches in Connected apps), one-time upload links for pictures and PDFs, what leaves the computer, renewal, the connection states, the errors a web app can see, and the copy-paste instructions for web agents.

AI, LLMs & AgentsIn 1 list36

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.