What problem does it solve? When memory operations fail, searches return empty results, or add_memory calls error out, it is hard to tell whether the cause is a missing API key, a broken session hook, or a connectivity issue. This Skill runs a structured diagnostic that pinpoints exactly which part of the mem0 plugin is failing. ## Core Features & Use Cases - Six-check diagnostic: Validates the MEM0_API_KEY, identity resolution (user_id, project_id, branch), memory tool connectivity via search_memories, write capability via add_memory/get_event_status/delete_memory, session context env vars, and auto-dream gate eligibility. - Deep quality scan (--deep): Detects duplicate, stale, low-confidence, contradictory, and untagged memories across the project scope. - Use Case: After search_memories returns empty results, run the status check to discover the MEM0_APP_ID env var was never injected because the shell.env hook did not fire, then restart OpenCode to fix it. ## Quick Start Ask the assistant to run the mem0 status diagnostic to verify the plugin's API key, connectivity, and memory read/write health.
