health

Diagnoses mem0 connectivity, API key validity, and memory read/write functionality.

1|Updated Jan 13, 2022
One-click install
npx skills add https://github.com/jayho-k/TIL --skill health-jayho-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/jayho-k/TIL/tree/main/AI/mem0/code/mem0_code_analize/mem0/integrations/mem0-plugin/skills/health
Command: npx skills add https://github.com/jayho-k/TIL --skill health-jayho-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When mem0 memory operations fail, searches return empty results, or MCP connections drop, developers lack a systematic way to pinpoint whether the issue is the API key, identity resolution, connectivity, or write capability. ## Core Features & Use Cases - Five-Point Diagnostic: Checks API key configuration, identity resolution (user/project/branch), MCP server connectivity, memory write/read capability, and session stats tracking in one pass. - Deep Quality Scan: With the --deep flag, detects duplicate, stale, low-confidence, contradictory, and untagged memories across your mem0 store. - Use Case: After add_memory calls start erroring in a coding session, run the health check to get a PASS/FAIL summary per component plus targeted troubleshooting steps for each failure. ## Quick Start Ask the assistant to run the mem0 health check to diagnose why memory operations are failing.

Frequently Asked Questions about health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot mem0 memory operations failing?

Run the health check, which executes five diagnostics covering API key configuration, identity resolution, MCP connectivity, write capability, and session stats. It reports PASS or FAIL per check and adds troubleshooting steps for any failure.

How to check if a mem0 API key is configured correctly?

The health check reads MEM0_API_KEY or CLAUDE_PLUGIN_OPTION_MEM0_API_KEY and prints only the first six characters for verification. If neither variable is set, it reports the key as NOT_SET and marks the check as failed.

Why does mem0 search return empty results?

Empty results often stem from wrong user_id or project_id filters, an invalid API key, or a dropped MCP connection. The health check verifies identity resolution and tests search_memories with the active filters to isolate the cause.

Can I detect duplicate or stale memories in mem0?

Yes, invoke the health check with the --deep flag to scan for duplicates, stale session states, low-confidence entries, contradictions, and untagged memories. It summarizes counts per category and suggests running the dream skill to fix issues.

What happens when the mem0 health write check stays pending?

The check writes a probe memory with infer disabled and polls get_event_status for the returned event_id. If the status remains PENDING after five seconds, it still passes because the write was accepted and processing is merely delayed.