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 Status Check

by mem0ai in mem0ai/mem0

Runs a four-part diagnostic on the mem0 plugin, checking the API key, identity resolution, memory search and memory write, then reports one pass-or-fail summary.

Apache-2.0Auto-check passedDevelopment

Install Mem0 Status Check

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

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

GitHub CLI
$ gh skill install mem0ai/mem0 mem0-status --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-status .claude/skills/mem0-status && 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-status
GitHub stars
67k
Token cost
~1.5k tokens
SKILL.md length
611 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
Apache-2.0

At a glance

Runs a four-part diagnostic on the mem0 plugin, checking the API key, identity resolution, memory search and memory write, then reports one pass-or-fail summary.

  • Memory search or add_memory calls are failing
  • SKILL.md covers Execution, Extended mode: Memory Quality… and Output formatting
  • Needs MEM0_API_KEY
  • Verifying the mem0 plugin is configured correctly after setup

What it does

Check one confirms an API key is set, printing only its first six characters. Check two resolves identity from the MEM0_* environment variables the plugin's shell.env hook already set, reporting user_id, project_id, branch and default_scope verbatim rather than re-deriving them from git, since re-shelling git can disagree with the plugin's resolved values and produce an inconsistent report.

Check three calls search_memories with a test query and passes on any successful response, even an empty one. Check four calls add_memory with a disposable health-check note, polls get_event_status for the asynchronous write, and on success deletes the created memory to clean up. All four checks run regardless of earlier failures, and the skill prints one combined summary at the end rather than stopping on the first problem.

When your agent uses it

  • Memory search or add_memory calls are failing
  • Verifying the mem0 plugin is configured correctly after setup
  • Searches are returning empty and a connectivity problem needs ruling out

Example prompts

  • “Run the mem0 status check, my memory searches keep coming back empty.”
  • “Check whether my mem0 API key and identity are set up correctly.”
  • “Diagnose why add_memory keeps failing in this project.”

Requirements

  • A configured MEM0_API_KEY environment variable
  • The mem0 OpenCode plugin

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

    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:

    • MEM0_API_KEY

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

Context cost

Mem0 Status Check loads about 1.5k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 611 words of instructions outside code blocks.

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

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). 611 words, ~1,513 tokens.

Download SKILL.mdSave it as .claude/skills/mem0-status/SKILL.md (or your agent's skills folder).
name
mem0-status
description
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, add_memory errors occur, or to verify the plugin is working correctly.

Mem0 Status

Run a diagnostic check on the mem0 plugin. Useful for troubleshooting.

Execution

Run ALL checks, then display a single summary. Do not stop on the first failure.

Check 1: API key
bash
_KEY="${MEM0_API_KEY:-}"
[ -n "$_KEY" ] && echo "${_KEY:0:6}..." || echo "NOT_SET"
  • If NOT_SET: FAIL — "No API key configured"
  • If set: PASS — the command already prints only the first 6 chars
Check 2: Identity resolution

Resolve identity from the MEM0_* environment variables set by the plugin's shell.env hook. These are the exact values the plugin uses to scope memories, so report them directly. Do NOT re-run git here: the plugin already resolved branch and project from git at session start, and re-shelling git can disagree with it — e.g. it prints an empty branch that renders as (not a git repo) while the Session check below shows branch=main. One source of truth keeps the two lines consistent.

bash
echo "user_id=${MEM0_USER_ID:-${USER:-default}}"
echo "project_id=${MEM0_APP_ID:-}"
echo "branch=${MEM0_BRANCH:-main}"
_S="$HOME/.mem0/settings.json"
_SCOPE="$(grep -o '"default_scope"[[:space:]]*:[[:space:]]*"[a-z]*"' "$_S" 2>/dev/null | grep -o '[a-z]*"$' | tr -d '"')"
echo "default_scope=${_SCOPE:-project}"
  • user_id: from MEM0_USER_ID, falling back to $USER
  • project_id: from MEM0_APP_ID
  • branch: from MEM0_BRANCH (the plugin's resolved value; falls back to main outside a git repo)
  • default_scope: from ~/.mem0/settings.json (default_scope), falling back to project. This is the scope memory tools use when none is given; change it with /mem0-scope.

PASS if user_id and project_id are non-empty. WARN if project_id is empty — the shell.env hook may not have fired (restart OpenCode). Report the branch verbatim from MEM0_BRANCH; never invent a string like (not a git repo).

Check 3: Memory tool connectivity

Call search_memories with:

  • query="health check"

  • filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": "<active_project_id>"}]}

  • top_k=1

  • If returns successfully (even empty): PASS

  • If errors: FAIL — show the error message

Check 4: Memory write capability

Call add_memory with:

  • text="Health check probe — safe to delete."
  • user_id=<active_user_id>
  • app_id=<active_project_id>
  • metadata={"type": "health_check", "probe": true}
  • infer=False

The response returns event_id (v3 writes are async). Call get_event_status(event_id=<event_id>) to check processing.

  • If status is SUCCEEDED: PASS — extract the memory ID from the event result, then call delete_memory with that ID to clean up.
  • If status is PENDING after 5 seconds: PASS (write accepted, processing delayed)
  • If errors: FAIL — show the error.
Check 5: Session context

Check that the plugin's shell.env hook has injected session context into the environment:

bash
echo "session_id=${MEM0_SESSION_ID:-}"
echo "app_id=${MEM0_APP_ID:-}"
echo "branch=${MEM0_BRANCH:-}"
  • If all three are non-empty: PASS — "Session active"
  • If any are missing: WARN — "Plugin env vars not set; shell.env hook may not have fired"
Show full SKILL.md (246 more words)Show less
Display
## mem0 status

PASS  API Key         m0-dVe...
PASS  Identity        user=kartik, project=mem0, branch=main
PASS  Default scope   project
PASS  Memory Tools    142ms
PASS  Write/Read      write + delete OK
PASS  Session         session_id=abc123, app_id=mem0, branch=main

All checks passed.

If any check fails, add a ## Troubleshooting section with specific fix steps for each failure.

Extended mode: Memory Quality Analysis

When invoked with --deep (e.g., /mem0-status --deep), run the standard 5 checks above plus a memory quality scan.

Quality Check 1: Duplicates

Call get_memories with filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": "<active_project_id>"}]}, page_size=200. Compare all pairs within the same metadata.type group for high textual overlap (shared nouns/keywords > 60%). Report:

Potential duplicates: <N> pairs
  [mem0:<id1>] ≈ [mem0:<id2>] — both about "<shared topic>"
Quality Check 2: Stale memories

Flag memories where:

  • metadata.type is session_state or compact_summary AND older than 90 days
  • metadata.confidence < 0.3 AND older than 30 days
Stale candidates: <N>
  [mem0:<id>] — session_state, 142d old
Quality Check 2b: Low-confidence memories

Flag memories where metadata.confidence < 0.5 (regardless of age). Report separately from stale:

Low-confidence memories: <N>
  [mem0:<id>] — confidence=0.3, "<content preview>"
Quality Check 3: Contradictions

Within each metadata.type group, flag pairs that assert opposing facts about the same topic. Use semantic judgment — look for negation patterns, conflicting tool/framework choices, or reversed decisions.

Possible contradictions: <N>
  [mem0:<idA>] vs [mem0:<idB>] — conflicting on "<topic>"
Quality Check 4: Orphan memories

Memories with no metadata.type set, or with metadata.type not in the 17 known coding categories. These were likely written without proper tagging.

Untagged/orphan memories: <N>
Quality summary
## Memory Quality

Duplicates: <N> · Stale: <N> · Contradictions: <N> · Orphans: <N>

If all counts are 0: Memory quality: clean. If any non-zero, list the affected memory IDs so the user can review them with the normal search, update, and delete tools.

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-status of mem0ai/mem0.

Open the folder on GitHubat commit b7ad69a

Compare with similar skills

Mem0 Status Check 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 Status Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mem0 Status Check this skillmem0ai/mem067k—~1.5kAutomated safety check: PassApache-2.0
Agenticx Memory ArchitectDemonDamon/AgenticX315—~1.1kAutomated safety check: PassApache-2.0
Hyperspacedb MemoryYARlabs/hyperspace-db162—~880Automated safety check: PassMIT
Self Improving Systemsooiyeefei/ccc494—~5.2kAutomated safety check: PassMIT
Mem0Anil-matcha/awesome-muse-connectors1.3k—~867Automated safety check: PassMIT
Commit Context Lookuprohitg00/agentmemory29k—~522Automated 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.

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

    162 GitHub stars~880 tokensUpdated yesterday
    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 4 days ago
    Agent WorkflowsAuto-check passed

  • Commit Context Lookup

    rohitg00/agentmemory

    Traces a file, function or line back to the agent session behind its current commit, using git blame and a memory lookup, and reports only what the records show.

    29k GitHub stars~522 tokensUpdated today
    DevelopmentAuto-check passed

  • Beacon Memory Distill

    Asymptote-Labs/agent-beacon

    Turn recorded agent sessions (Beacon traces from Claude Code, Cursor, Codex, OpenCode, and other harnesses) into reviewed, reusable project memory.

    1.8k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-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 1 repo~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 today
    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 today
    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 today
    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 today
    Auto-check passed

  • Mem0 Memory Scope

    mem0ai/mem0

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

    67k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mem0 Status Check

What does Mem0 Status Check do?

Runs a four-part diagnostic on the mem0 plugin, checking the API key, identity resolution, memory search and memory write, then reports one pass-or-fail summary. Check one confirms an API key is set, printing only its first six characters.env hook already set, reporting user_id, project_id, branch and default_scope verbatim rather than re-deriving them from git, since re-shelling git can disagree with the plugin's resolved values and produce an inconsistent report.

When should I use Mem0 Status Check?

Mem0 Status Check fits situations like: memory search or add_memory calls are failing; verifying the mem0 plugin is configured correctly after setup; searches are returning empty and a connectivity problem needs ruling out.

How do I install Mem0 Status Check in Claude Code?

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

How do I install Mem0 Status Check in Codex?

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

Can I use Mem0 Status Check 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-status -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-status, .gemini/skills/mem0-status, .github/skills/mem0-status and .opencode/skills/mem0-status in your project.

What does Mem0 Status Check need to run?

Going by SKILL.md and its folder, Mem0 Status Check needs credentials named MEM0_API_KEY. Our summary lists: A configured MEM0_API_KEY environment variable; The mem0 OpenCode plugin.

Does Mem0 Status Check 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 Status Check 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 Status Check use?

Mem0 Status Check 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 Status Check use?

About 1.5k tokens (SKILL.md is roughly 6.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 Mem0 Status Check?

Skills that share tags, products or a category with Mem0 Status Check: Agenticx Memory Architect (DemonDamon/AgenticX, 315 stars), Hyperspacedb Memory (YARlabs/hyperspace-db, 162 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 Status Check?

mem0ai (a GitHub organization) maintains it in mem0ai/mem0, which has 66,867 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 9, 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.