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

Mem0 Memory Scope

by mem0ai in mem0ai/mem0

Shows or changes the default Mem0 memory scope, project, session or global, which decides where memories are saved and searched.

Apache-2.0Auto-check passedAgent Workflows

Install Mem0 Memory Scope

skills CLI
$ npx skills add mem0ai/mem0 --skill mem0-scope -a claude-code

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

GitHub CLI
$ gh skill install mem0ai/mem0 mem0-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/mem0ai/mem0.git skills-src && mkdir -p .claude/skills && cp -r skills-src/integrations/opencode-plugin/opencode-skills/mem0-scope .claude/skills/mem0-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
mem0-scope
GitHub stars
67k
Token cost
~1.1k tokens
SKILL.md length
480 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
Apache-2.0

At a glance

Shows or changes the default Mem0 memory scope, project, session or global, which decides where memories are saved and searched.

  • Works in 3 steps: Determine intent → View mode — show the current scope → Change mode — set a new scope
  • Checking which Mem0 memory scope is currently active
  • SKILL.md covers Execution and Output formatting
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The default scope is what the memory tools use when no explicit scope is given. It is stored as default_scope in ~/.mem0/settings.json and read fresh on each memory operation, so a change applies immediately in the current session. There are three scopes. Project, the default, covers this repo only and filters by user and app. Session covers this run only by adding the run id. Global spans all your projects, searching across every app and saving memories without an app id so they are user-wide.

If your message names no scope, the agent shows the current one, falling back to project when nothing is set, optionally with a count of the memories in it and an active marker beside it. If it names project, session or global (repo, run and all or everywhere are accepted as aliases), the agent validates the value, reads the existing settings and writes the file back with only default_scope changed, keeping other keys such as global_search and auto_save. The excerpt is cut off in the example output.

When your agent uses it

  • Checking which Mem0 memory scope is currently active
  • Isolating memories to the current session only
  • Sharing memories across all of your projects
  • Switching back to memories kept for this repo alone

Example prompts

  • “What memory scope am I using?”
  • “Switch my default memory scope to global.”
  • “Keep memories for this session only.”

Requirements

  • The Mem0 OpenCode plugin and its memory tools

Workflow steps

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

  1. Determine intent
  2. View mode — show the current scope
  3. Change mode — set a new scope

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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

Mem0 Memory Scope loads about 1.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 480 words of instructions outside code blocks.

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

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 mem0ai/mem0 at commit b7ad69a, republished under its Apache-2.0 licence (© mem0ai). 480 words, ~1,133 tokens.

Download SKILL.mdSave it as .claude/skills/mem0-scope/SKILL.md (or your agent's skills folder).
name
mem0-scope
description
Views or changes the default memory scope (project, session, or global) used when saving and searching memories. Use when the user wants to control whether memories are scoped to this repo, this run, or shared across all their projects.

Mem0 Scope

View or change the default memory scope — the scope the memory tools use when no explicit scope is given. The setting persists in ~/.mem0/settings.json (default_scope) and the plugin reads it fresh on each memory operation, so a change takes effect immediately in the current session.

The three scopes:

  • project (default) — this repo only. Filters by user_id + app_id.
  • session — this run only. Adds run_id (the current session) so memories are isolated to this conversation.
  • global — across ALL your projects. Reads use app_id="*"; writes drop app_id so the memory is user-wide.

Execution

Step 1: Determine intent

Look at the user's message for a target scope word: project, session, or global (also accept "repo"→project, "run"→session, "all"/"everywhere"→global).

  • No target word present → View mode (Step 2).
  • A target word present → Change mode (Step 3).
Step 2: View mode — show the current scope

  1. Read the current default scope from settings:

    bash
    _S="$HOME/.mem0/settings.json"
[ -f "$_S" ] && grep -o '"default_scope"[[:space:]]*:[[:space:]]*"[a-z]*"' "$_S" | grep -o '[a-z]*"$' | tr -d '"' || echo "project"

    If the command prints nothing, the scope is project (the default).

  2. (Optional) Show how many memories live in the current scope by calling get_memories with scope="<current>", page_size=1, and reading the count (or result length) from the response.

  3. Display using the identity the plugin exported (do NOT re-shell git):

    Mem0 memory scope

Current default scope: <current>

  project  - this repo only (user + app_id)        <marker if active>
  session  - this run only (adds run_id)           <marker if active>
  global   - all your projects (app_id = *)         <marker if active>

User:    ${MEM0_USER_ID}
Project: ${MEM0_APP_ID}
Session: ${MEM0_SESSION_ID}

To change: /mem0-scope session    (or project / global)

    Put [active] next to the current scope. If you fetched a count in step 2, add a Memories in scope: <N> line.

Show full SKILL.md (293 more words)Show less
Step 3: Change mode — set a new scope

  1. Validate the target is one of project, session, global. If not, show the three options and stop.

  2. Read the existing settings so you preserve every other key. Use the Read tool on ~/.mem0/settings.json (it may not exist yet — treat a missing file as {}).

  3. Write the file back with the Write tool, keeping ALL existing keys and only setting "default_scope" to the target. Pretty-print with 2-space indent and a trailing newline. Do not drop global_search, auto_save, or any other field that was present.

    Example resulting file (when other keys already existed):

    json
    {
  "auto_save": true,
  "search_limit": 10,
  "default_scope": "global"
}

  4. Confirm:

    Default memory scope changed: <old> -> <new>

<one line describing the effect — see below>
Applies immediately to memory tools in this session.

To revert: /mem0-scope <old>

    Effect lines:

    • project → "New memories and searches are limited to this repo."
    • session → "New memories and searches are limited to this run (this conversation)."
    • global → "New memories and searches span all your projects. delete_all_memories still needs an explicit scope=global to delete user-wide."
Notes
  • This only changes the default. Any memory tool call can still pass an explicit scope to override it for that one call.
  • delete_all_memories deliberately ignores the default scope: deleting user-wide always requires an explicit scope="global", so changing the default can never turn a routine cleanup into a cross-project wipe.
  • global scope (this user, all their projects) is distinct from the separate global_search setting (all users). Leave global_search untouched here.

Output formatting

IMPORTANT: Do NOT use markdown in your output. OpenCode TUI renders text verbatim — markdown like bold, ## headers, and | table | syntax appears as raw characters. Use plain text with indentation for structure. Use dashes for lists. Use spaces to align columns instead of markdown tables.

© mem0ai, Apache-2.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 integrations/opencode-plugin/opencode-skills/mem0-scope of mem0ai/mem0.

Open the folder on GitHubat commit b7ad69a

Compare with similar skills

Mem0 Memory 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.

Mem0 Memory Scope compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mem0 Memory Scope this skillmem0ai/mem067k—~1.1kAutomated safety check: PassApache-2.0
Agenticx Memory ArchitectDemonDamon/AgenticX294—~1.1kAutomated safety check: PassApache-2.0
Hyperspacedb MemoryYARlabs/hyperspace-db161—~880Automated safety check: PassMIT
Self Improving Systemsooiyeefei/ccc494—~5.2kAutomated safety check: PassMIT
Mem0Anil-matcha/awesome-muse-connectors1.3k—~867Automated safety check: PassMIT
Mem0majiayu000/claude-skill-registry6661 repos~1.8kAutomated safety check: PassApache-2.0

Similar skills

  • Agenticx Memory Architect

    DemonDamon/AgenticX

    Guide for setting up and using the AgenticX memory system including Mem0 integration, long-term memory, context management, and memory-enhanced agents.

    294 GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Hyperspacedb Memory

    YARlabs/hyperspace-db

    Zero-overhead cognitive long-term and episodic memory for AI agents (Mem0 drop-in and mcp-hyperspace-memory).

    161 GitHub stars~880 tokensUpdated 29 days ago
    Agent WorkflowsAuto-check passed

  • Self Improving Systems

    ooiyeefei/ccc

    Decide whether your agent actually needs persistent memory, feedback loops, or closed-loop learning, then design the smallest thing that pays for itself.

    494 GitHub stars~5.2k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

  • Mem0

    Anil-matcha/awesome-muse-connectors

    Mem0 memory CLI: add memories from messages, semantic search, read or delete memories, poll async events.

    1.3k GitHub stars~867 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Mem0

    majiayu000/claude-skill-registry

    Adds persistent, personalized long-term memory to LLM apps and agents with Mem0, the open-source memory layer: it extracts facts from conversations, stores them in a vector database and retrieves…

    666 GitHub starsUsed in 1 repo~1.8k tokens
    DatabasesAuto-check passed

  • Mem0 Bridge

    momori777/Artemis

    Mem0 memory bridge for AI Girlfriend — search/read/write long-term memories from Qdrant vector DB.

    377 GitHub stars~453 tokensUpdated 8 days ago
    Media & CreativeAuto-check passed

More from mem0ai/mem0

All 26 skills in this repo

  • Mem0 Platform SDK

    mem0ai/mem0

    Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.

    67k GitHub starsUsed in 2 repos~2.2k tokens
    Auto-check passed

  • Mem0 CLI Memory Commands

    mem0ai/mem0

    Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.

    67k GitHub stars~2k tokensUpdated yesterday
    Auto-check: notes

  • Mem0 Provider for Vercel AI SDK

    mem0ai/mem0

    Adds persistent memory to Vercel AI SDK apps with the Mem0 provider, using a wrapped model or standalone retrieve and store utilities.

    67k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Mem0 Memory Deletion

    mem0ai/mem0

    Finds and deletes specific mem0 memories by search query or ID, always asking for confirmation first, and can undo the most recent memories added this session.

    67k GitHub stars~664 tokensUpdated yesterday
    Auto-check passed

  • Mem0 Remember Command

    mem0ai/mem0

    Saves a fact, decision or preference the user states into mem0 as written, labeled with a memory type such as decision, convention or user_preference.

    67k GitHub stars~560 tokensUpdated yesterday
    Auto-check passed

  • Mem0 Memory Search

    mem0ai/mem0

    Looks up stored agent memories by keyword or ID and prints compact one-line results instead of full detail.

    67k GitHub stars~502 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Mem0 Memory Scope

What does Mem0 Memory Scope do?

Shows or changes the default Mem0 memory scope, project, session or global, which decides where memories are saved and searched. The default scope is what the memory tools use when no explicit scope is given.json and read fresh on each memory operation, so a change applies immediately in the current session.

When should I use Mem0 Memory Scope?

Mem0 Memory Scope fits situations like: checking which Mem0 memory scope is currently active; isolating memories to the current session only; sharing memories across all of your projects; switching back to memories kept for this repo alone.

How do I install Mem0 Memory Scope in Claude Code?

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

How do I install Mem0 Memory Scope in Codex?

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

Can I use Mem0 Memory 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 mem0ai/mem0 --skill mem0-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/mem0-scope, .gemini/skills/mem0-scope, .github/skills/mem0-scope and .opencode/skills/mem0-scope in your project.

What does Mem0 Memory Scope need to run?

SKILL.md names no scripts, command-line tools or credentials: Mem0 Memory Scope is instructions for the agent only. Our summary lists: The Mem0 OpenCode plugin and its memory tools.

Does Mem0 Memory 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 Mem0 Memory Scope 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 Mem0 Memory Scope use?

Mem0 Memory Scope is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mem0 Memory Scope use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Mem0 Memory Scope?

Skills that share tags, products or a category with Mem0 Memory Scope: Agenticx Memory Architect (DemonDamon/AgenticX, 294 stars), Hyperspacedb Memory (YARlabs/hyperspace-db, 161 stars), Self Improving Systems (ooiyeefei/ccc, 494 stars) and Mem0 (Anil-matcha/awesome-muse-connectors, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mem0 Memory Scope?

mem0ai (a GitHub organization) maintains it in mem0ai/mem0, which has 66,788 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.

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