Agent skill

Slm Mesh

by qualixar in qualixar/superlocalmemory

Cross-session peer coordination via the SLM mesh network. An agent skill from qualixar/superlocalmemory.

AGPL-3.0Auto-check: notesAgent Workflows

Install Slm Mesh

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

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

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

At a glance

Cross-session peer coordination via the SLM mesh network. An agent skill from qualixar/superlocalmemory.

  • Works in 8 steps: mesh_summary — announce what this… → mesh_peers — list active sessions → mesh_send — send a message to another… → …
  • Tasks that involve Session handoff
  • SKILL.md covers Profile requirement, Tool reference, Common workflow: parallel… and Mesh vs memory: when to use…, plus 2 more sections
  • Needs SLM_MESH_SHARED_SECRET

What it does

Slm Mesh is an agent skill from qualixar/superlocalmemory. Cross-session peer coordination via the SLM mesh network. Lets multiple AI agent sessions on the same machine discover each other, send messages, share lightweight state, and lock files to avoid conflicts. 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; the other tools are MCP-only.

Its SKILL.md is about 2.3k 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, covering Session handoff and MCP servers. 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

  • Tasks that involve Session handoff
  • Tasks that involve MCP servers

Example prompts

  • “/slm-mesh”

Requirements

  • A credential in SLM_MESH_SHARED_SECRET
  • Pre-approved tools (allowed-tools): mesh_summary, mesh_peers, mesh_send, mesh_inbox, mesh_state, mesh_lock, mesh_events, mesh_status, Bash

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. mesh_summary — announce what this session is doing
  2. mesh_peers — list active sessions
  3. mesh_send — send a message to another session
  4. mesh_inbox — read messages sent to this session
  5. mesh_state — get or set shared coordination state
  6. mesh_lock — file lock coordination
  7. mesh_events — recent mesh activity log
  8. mesh_status — mesh broker health

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:

    • mesh_summary
    • mesh_peers
    • mesh_send
    • mesh_inbox
    • mesh_state
    • mesh_lock
    • mesh_events
    • mesh_status
    • Bash

    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 these keys or tokens, usually read from environment variables:

    • SLM_MESH_SHARED_SECRET

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

Context cost

Slm Mesh loads about 2.3k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 728 words of instructions outside code blocks.

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

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: mesh_summary, mesh_peers, mesh_send, mesh_inbox, mesh_state, mesh_lock, mesh_events, mesh_status, Ba

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). 728 words, ~2,274 tokens.

Download SKILL.mdSave it as .claude/skills/slm-mesh/SKILL.md (or your agent's skills folder).
name
slm-mesh
description
Cross-session peer coordination via the SLM mesh network. Lets multiple AI agent sessions on the same machine discover each other, send messages, share lightweight state, and lock files to avoid conflicts. 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; the other tools are MCP-only.
allowed-tools
mesh_summary, mesh_peers, mesh_send, mesh_inbox, mesh_state, mesh_lock, mesh_events, mesh_status, Bash
when_to_use
- Multiple agent sessions running simultaneously on the same machine - "Announce what I'm working on to other sessions" - "Check if another agent has locked a…

slm-mesh — Cross-Session Peer Coordination

The mesh network lets multiple AI agent sessions on the same machine discover each other and coordinate in real time — without writing to the persistent memory store. Mesh messages are transient (48-hour TTL); they complement memory (which is durable) rather than replacing it.

By default the mesh is local: the SLM daemon on this machine is the broker and nothing leaves it. Two machines can be joined only if the user sets SLM_MESH_PEER_URL and SLM_MESH_SHARED_SECRET for their daemons; then peers and messages cross to the other machine. Do not configure that yourself.


Profile requirement

Mesh tools are registered in the full, power and mesh MCP tool sets and in the default set that applies when the host configures none. They are not in core or code. The tool set is fixed when the MCP server starts, and switch_profile cannot change it (it changes the active memory profile). If the tools are missing, check SLM_MCP_PROFILE in the host's MCP config and ask the user before changing it. See slm-profile.


Tool reference

1. mesh_summary — announce what this session is doing
mesh_summary(summary: str = "") -> dict

Call at session start to register on the mesh and announce your purpose. Other sessions can see your summary via mesh_peers. The session stays alive via automatic heartbeat.

mesh_summary(summary="Refactoring auth module in api/src/auth/")

Response: {peer_id, summary, project_path, registered, heartbeat_active, broker_response}

Call this once at the start of any session that will participate in the mesh. The peer registration happens automatically at MCP startup, but calling mesh_summary sets the human-readable description that other agents see.


2. mesh_peers — list active sessions
mesh_peers() -> dict

Returns all active peer sessions on this machine.

mesh_peers()

Response: {peers: [{peer_id, summary, project_path, last_seen}], count, my_peer_id}

Use this to discover other sessions before sending a message or checking for conflicts.


3. mesh_send — send a message to another session
mesh_send(
  to: str,       # peer_id | "broadcast" | "project:/path/to/dir"
  message: str,  # max 4 KB — use file paths for large data
) -> dict

Send a targeted, broadcast, or project-wide message.

# Direct message to a specific peer
peers = await mesh_peers()
target_id = peers["peers"][0]["peer_id"]
mesh_send(to=target_id, message="I'm starting work on auth/handler.py — please hold off")

# Broadcast to all sessions
mesh_send(to="broadcast", message="Deploying to staging in 5 minutes")

# Message all sessions working in the same project
mesh_send(to="project:~/myproject", message="Tests are green on main")

4 KB message cap. For large payloads (diffs, file contents), write to a file and send the path instead. The circuit breaker opens automatically if the daemon is repeatedly unreachable — mesh_send returns ok: false in that case.


4. mesh_inbox — read messages sent to this session
mesh_inbox() -> dict

Returns unread messages (direct, broadcast, and project-targeted). Messages are automatically marked as read after retrieval.

inbox = await mesh_inbox()
for msg in inbox["messages"]:
    print(msg["from"], msg["content"])

Response: {messages: [{id, from, content, sent_at, read}], count, unread}

Messages auto-expire after 48 hours.


5. mesh_state — get or set shared coordination state
mesh_state(
  key: str = "",
  value: str = "",
  action: str = "get",   # "get" | "set"
) -> dict

Shared state is visible to all authenticated peers. Use it for non-secret coordination metadata: feature flags, task assignments, progress markers.

# Set state
mesh_state(key="deploy_in_progress", value="true", action="set")
mesh_state(key="current_reviewer", value=my_peer_id, action="set")

# Read one key
mesh_state(key="deploy_in_progress", action="get")

# Read all state
mesh_state(action="get")

Security constraint: Credentials, tokens, passwords, and API keys are rejected by the broker. Never store secrets in shared state.


Show full SKILL.md (306 more words)Show less
6. mesh_lock — file lock coordination
mesh_lock(
  file_path: str,         # must be an absolute path
  action: str = "query",  # "query" | "acquire" | "release"
) -> dict

Check, acquire, or release a file lock before editing a shared file.

# Step 1: check if the file is already locked
lock = await mesh_lock(file_path="/abs/path/to/auth/handler.py", action="query")

if lock.get("locked"):
    print(f"File is locked by {lock['locked_by']} — wait")
else:
    # Step 2: acquire the lock
    mesh_lock(file_path="/abs/path/to/auth/handler.py", action="acquire")

    # ... edit the file ...

    # Step 3: release the lock when done
    mesh_lock(file_path="/abs/path/to/auth/handler.py", action="release")

file_path must be an absolute path (starts with / on Unix, drive letter on Windows). Relative paths are rejected.


7. mesh_events — recent mesh activity log
mesh_events() -> dict

Returns the activity log for the mesh network: peer joins, leaves, messages sent, and state changes. Use to understand what other sessions have been doing.


8. mesh_status — mesh broker health
mesh_status() -> dict

Returns broker uptime, peer count, and connection health. Use at session start to confirm the mesh is available before relying on coordination.

Response includes: broker_up, peer_count (active peers, with remote_peer_count, local_session_count and stale counts alongside), uptime_s, my_peer_id, heartbeat_active.


Common workflow: parallel agents coordinating on a shared repo

# Both agents call at session start:
await mesh_summary(summary="Working on feature/auth-refactor")

# Agent A: check who else is active
peers = await mesh_peers()
# → sees Agent B working on the same project

# Agent A: before editing a shared file
lock = await mesh_lock("/repo/src/auth/handler.py", action="query")
if not lock.get("locked"):
    await mesh_lock("/repo/src/auth/handler.py", action="acquire")
    # ... edit handler.py ...
    await mesh_lock("/repo/src/auth/handler.py", action="release")

# Agent A: after finishing a phase
await mesh_send(to="project:/repo", message="Auth refactor complete — handler.py ready for review")

# Agent B: check inbox
inbox = await mesh_inbox()

Mesh vs memory: when to use which

NeedUse
Ephemeral coordination signal (< 48h)mesh_send / mesh_state
Durable fact across sessions/daysremember
File conflict preventionmesh_lock
Cross-profile fact sharingscope="shared"/"global" on remember
Session announcementmesh_summary
Finding parallel agentsmesh_peers

Error handling

All 8 mesh tools return structured errors — they never raise exceptions.

ErrorCauseAction
broker_up: false from mesh_statusDaemon not running or mesh not configuredRun slm mesh status (prints the broker's answer) or slm status to check daemon health
ok: false from mesh_send with circuit-breaker messageRepeated daemon unreachabilityDaemon unreachable; stop sending until broker is up
ok: false from mesh_lockLock operation failedCheck file_path is absolute; retry once
Empty peers from mesh_peersNo other sessions registeredYou're the only active session

Mesh failures are non-fatal for the primary task. If mesh_status shows broker_up: false, proceed without mesh coordination — do not block work on mesh availability.


  • slm-profile — which tool sets include the mesh tools
  • slm-scope — for durable cross-profile sharing (complement to transient mesh state)
  • slm-remember — persist coordination decisions that should survive session end
  • slm-governance — enterprise governance of mesh (who can send/receive)

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-mesh of qualixar/superlocalmemory.

Open the folder on GitHubat commit 26f8c68

Compare with similar skills

Slm Mesh 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 Mesh compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slm Mesh this skillqualixar/superlocalmemory231—~2.3kAutomated safety check: NotesAGPL-3.0
Memori MCP Memory UsageMemoriLabs/Memori17k—~3.8kAutomated safety check: PassMIT
Engraphis MemoryCoding-Dev-Tools/engraphis179—~3.7kAutomated safety check: PassApache-2.0
MemorixAVIDS2/memorix837—~516Automated safety check: PassApache-2.0
Engram MemoryPatdolitse/piia-engram163—~1.3kAutomated safety check: PassAGPL-3.0-or-later
Prism Startup Contextdcostenco/prism-coder158—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Memori MCP Memory Usage

    MemoriLabs/Memori

    Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.

    17k GitHub stars~3.8k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Engraphis Memory

    Coding-Dev-Tools/engraphis

    Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools.

    179 GitHub stars~3.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Memorix

    AVIDS2/memorix

    A skill your agent uses when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.

    837 GitHub stars~516 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Engram Memory

    Patdolitse/piia-engram

    Routes continuity and recall requests to Engram, a local-first MCP memory and identity layer that saves user-approved lessons, decisions and playbooks.

    163 GitHub stars~1.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Prism Startup Context

    dcostenco/prism-coder

    Loads Prism session memory on the first user turn, greets the developer by their configured name and shows recent-session context at the configured depth.

    158 GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Mnemos

    jeremylongshore/tons-of-skills-marketplace

    Persistent memory and learning-loop skills for AI coding agents using mnemos MCP tools.

    2.8k GitHub stars~3.1k tokensUpdated today
    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.

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

    231 GitHub stars~3k tokensUpdated today
    Auto-check: notes
  • Slm Loop

    qualixar/superlocalmemory

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

    231 GitHub stars~2k tokensUpdated today
    Auto-check: notes
  • Slm Recall

    qualixar/superlocalmemory

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

    231 GitHub stars~5.1k tokensUpdated today
    Auto-check: notes
  • Slm Remember

    qualixar/superlocalmemory

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

    231 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).

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

Categories

Questions about Slm Mesh

What does Slm Mesh do?

Cross-session peer coordination via the SLM mesh network. An agent skill from qualixar/superlocalmemory. Slm Mesh is an agent skill from qualixar/superlocalmemory. Cross-session peer coordination via the SLM mesh network.

When should I use Slm Mesh?

Slm Mesh fits situations like: tasks that involve Session handoff; tasks that involve MCP servers.

How do I install Slm Mesh in Claude Code?

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

How do I install Slm Mesh in Codex?

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

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

What does Slm Mesh need to run?

Going by SKILL.md and its folder, Slm Mesh needs credentials named SLM_MESH_SHARED_SECRET. Our summary lists: A credential in SLM_MESH_SHARED_SECRET. Its frontmatter pre-approves these tools: mesh_summary, mesh_peers, mesh_send, mesh_inbox, mesh_state, mesh_lock, mesh_events, mesh_status, Bash.

Does Slm Mesh 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 Mesh 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 Mesh use?

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

About 2.3k tokens (SKILL.md is roughly 9.1k 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 Mesh?

Skills that share tags, products or a category with Slm Mesh: Memori MCP Memory Usage (MemoriLabs/Memori, 17k stars), Engraphis Memory (Coding-Dev-Tools/engraphis, 179 stars), Memorix (AVIDS2/memorix, 837 stars) and Engram Memory (Patdolitse/piia-engram, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slm Mesh?

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