status

Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Memory status

Run both commands and report the combined result in plain language:

python3 "${CLAUDE_PLUGIN_ROOT}/core/memory_cli.py" --harness "claude-code" --plugin-data-dir "${CLAUDE_PLUGIN_DATA}" status --json
python3 "${CLAUDE_PLUGIN_ROOT}/core/memory_cli.py" --harness "claude-code" --plugin-data-dir "${CLAUDE_PLUGIN_DATA}" doctor

Summarize, using only fields the JSON actually reports: whether capture is active or paused, the user ID and repository scope (repo_id), whether an API key is configured, the event/flush/retrieval counts (flushes is the number of completed flushes, not a pending count), and the doctor check results. If doctor reports an authentication failure (401 / invalid key), say clearly that the Mem0 API key is invalid or expired and that memories are NOT being created. Never report an auth failure as "no memories found". Suggest reinstalling with --config api_key=... in that case.

Repository: mem0ai/mem0
Path: integrations/claude-code-plugin/skills/status/SKILL.md
Commit: 0df3e4b

Last updated: 2 days ago
First committed: 10 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.