Agent skill · mem0ai
mem0-status
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.
What it needs
About 3k tokens when loaded.
What this skill does
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 If NOTSET: 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. userid: from MEM0USERID, falling back to $USER projectid: from MEM0APPID branch: from MEM0BRANCH (the plugin's resolved value; falls back to main outside a git repo) defaultscope: from ~/.mem0/settings.json (defaultscope), falling back to project. This is the scope memory tools use when none is given; change it with /mem0-scope. PASS if userid and projectid are non-empty. WARN if projectid is empty — the shell.env hook may not have fired (restart OpenCode). Report the branch verbatim from MEM0BRANCH; never invent a string like (not a git repo). Check 3: Memory tool connectivity Call searchmemories with: query="health check" filters={"AND": [{"userid": "<activeuserid>"}, {"appid": "<activeprojectid>"}]} topk=1 If returns successfully (even empty): PASS If errors: FAIL — show the error message Check 4: Memory write capability Call addmemory with: text="Health check probe — safe to delete." userid=<activeuserid> appid=<activeprojectid> metadata={"type": "healthcheck", "probe": true} infer=False The response returns eventid (v3 writes are async). Call geteventstatus(eventid=<eventid>) to check processing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mem0ai/mem0-status--537dd4