Source profileQuality 89/100Review permissions

mem0ai/mem0/skills/mem0/SKILL.md

mem0

Mem0 Platform SDK for adding persistent memory to AI applications. TRIGGER when: user mentions "mem0", "MemoryClient", "memory layer", "remember user preferences", "persistent context", "personalization", or needs to add long-term memory to chatbots, agents, or AI apps. Covers Python SDK (mem0ai), TypeScript SDK (mem0ai), and framework integrations (LangChain, CrewAI, OpenAI Agents SDK, Pipecat, LlamaIndex, AutoGen, LangGraph). Also covers the open-source self-hosted Memory class. This is the DE

Source repository stars
62,498
Declared platforms
0
Static risk flags
1
Last source update
2026-08-04
Source checked
2026-08-04

Decision brief

What it does—and where it fits

Skill Graph: This skill is part of the Mem0 skill graph: - mem0 (this skill) -- Platform Client SDK + OSS (Python + TypeScript) - mem0-cli (GitHub) -- Command-line interface - mem0-vercel-ai-sdk (GitHub) -- Vercel AI SDK provider

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/mem0ai/mem0 --skill "skills/mem0"
    Safe inspection promptEditorial

    Inspect the Agent Skill "mem0" from https://github.com/mem0ai/mem0/blob/b54710a3c3b9060971b288197aee87efa3cc4d98/skills/mem0/SKILL.md at commit b54710a3c3b9060971b288197aee87efa3cc4d98. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Step 1: Install and authenticate

      Get an API key at: https://app.mem0.ai/dashboard/api-keys?utmsource=oss&utmmedium=skill-mem0

      Get an API key at: https://app.mem0.ai/dashboard/api-keys?utmsource=oss&utmmedium=skill-mem0Don't have a MEM0APIKEY? Run mem0 init --agent --agent-caller --json (after pip install mem0-cli or npm install -g @mem0/cli), substituting your agent identity (e.g. claude-code, cursor). If you forgot to pass --agent-c…
    2. 02

      Step 2: Initialize the client

      For async Python, use AsyncMemoryClient.

      For async Python, use AsyncMemoryClient.
    3. 03

      Step 3: Core operations

      Every Mem0 integration follows the same pattern: retrieve → generate → store.

      Every Mem0 integration follows the same pattern: retrieve → generate → store.
    4. 04

      Add memories

      Review the “Add memories” section in the pinned source before continuing.

      Review and apply the “Add memories” source section.
    5. 05

      Search memories

      Review the “Search memories” section in the pinned source before continuing.

      Review and apply the “Search memories” source section.

    Permission review

    Static risk signals and limitations

    Runs scripts

    medium · line 21

    The documentation asks the agent to run terminal commands or scripts.

    npm install mem0ai

    Runs scripts

    medium · line 135

    The documentation asks the agent to run terminal commands or scripts.

    python ${CLAUDE_SKILL_DIR}/scripts/mem0_doc_search.py --query "topic"

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score89/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars62,498SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    mem0ai/mem0
    Skill path
    skills/mem0/SKILL.md
    Commit
    b54710a3c3b9060971b288197aee87efa3cc4d98
    License
    Apache-2.0
    Collected
    2026-08-04
    Default branch
    main
    View the original SKILL.md

    Mem0 Platform Integration

    Skill Graph: This skill is part of the Mem0 skill graph:

    Mem0 is a managed memory layer for AI applications. It stores, retrieves, and manages user memories via API — no infrastructure to deploy. For self-hosted usage, see the OSS section in the client references below.

    Step 1: Install and authenticate

    Python:

    pip install mem0ai
    export MEM0_API_KEY="m0-your-api-key"
    

    TypeScript/JavaScript:

    npm install mem0ai
    export MEM0_API_KEY="m0-your-api-key"
    

    Get an API key at: https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=skill-mem0

    Don't have a MEM0_API_KEY? Run mem0 init --agent --agent-caller <your-name> --json (after pip install mem0-cli or npm install -g @mem0/cli), substituting your agent identity (e.g. claude-code, cursor). If you forgot to pass --agent-caller, run mem0 identify <your-name> after init. The human can claim later with mem0 init --email <your-email>.

    Step 2: Initialize the client

    Python:

    from mem0 import MemoryClient
    client = MemoryClient(api_key="m0-xxx")
    

    TypeScript:

    import MemoryClient from 'mem0ai';
    const client = new MemoryClient({ apiKey: 'm0-xxx' });
    

    For async Python, use AsyncMemoryClient.

    Step 3: Core operations

    Every Mem0 integration follows the same pattern: retrieve → generate → store.

    Add memories

    messages = [
        {"role": "user", "content": "I'm a vegetarian and allergic to nuts."},
        {"role": "assistant", "content": "Got it! I'll remember that."}
    ]
    client.add(messages, user_id="alice")
    

    Search memories

    results = client.search("dietary preferences", filters={"user_id": "alice"})
    for mem in results.get("results", []):
        print(mem["memory"])
    

    Get all memories

    all_memories = client.get_all(filters={"user_id": "alice"})
    

    Update a memory

    client.update("memory-uuid", text="Updated: vegetarian, nut allergy, prefers organic")
    

    Delete a memory

    client.delete("memory-uuid")
    client.delete_all(user_id="alice")  # delete all for a user
    

    Common integration pattern

    from mem0 import MemoryClient
    from openai import OpenAI
    
    mem0 = MemoryClient()
    openai = OpenAI()
    
    def chat(user_input: str, user_id: str) -> str:
        # 1. Retrieve relevant memories
        memories = mem0.search(user_input, filters={"user_id": user_id})
        context = "\n".join([m["memory"] for m in memories.get("results", [])])
    
        # 2. Generate response with memory context
        response = openai.chat.completions.create(
            model="gpt-5-mini",
            messages=[
                {"role": "system", "content": f"User context:\n{context}"},
                {"role": "user", "content": user_input},
            ]
        )
        reply = response.choices[0].message.content
    
        # 3. Store interaction for future context
        mem0.add(
            [{"role": "user", "content": user_input}, {"role": "assistant", "content": reply}],
            user_id=user_id
        )
        return reply
    

    Common edge cases

    • Search returns empty: Memories process asynchronously. Wait 2-3s after add() before searching. Also verify user_id matches exactly (case-sensitive) and use filters={"user_id": "..."} syntax.
    • AND filter with user_id + agent_id returns empty: Entities are stored separately. Use OR instead, or query separately.
    • Duplicate memories: Don't mix infer=True (default) and infer=False for the same data. Stick to one mode.
    • Wrong import: Always use from mem0 import MemoryClient (or AsyncMemoryClient for async). Do not use from mem0 import Memory.
    • v3 defaults: top_k=20, threshold=0.1, rerank=False. Adjust as needed for your use case.

    v2 Compatibility

    If you're using SDK v2.x, note these differences:

    • Entity IDs: Pass user_id as top-level kwarg to search() instead of inside filters
    • Defaults: top_k=100, no threshold, rerank=True
    • Graph memory: Available via enable_graph=True

    See the migration guide for details.

    Live documentation search

    For the latest docs beyond what's in the references, use the doc search tool:

    python ${CLAUDE_SKILL_DIR}/scripts/mem0_doc_search.py --query "topic"
    python ${CLAUDE_SKILL_DIR}/scripts/mem0_doc_search.py --page "/platform/features/graph-memory"
    python ${CLAUDE_SKILL_DIR}/scripts/mem0_doc_search.py --index
    

    No API key needed — searches docs.mem0.ai directly.

    Client SDK References

    Language-specific deep references (Platform + OSS):

    LanguageFile
    Python (MemoryClient + AsyncMemoryClient + Memory OSS)client/python.md
    TypeScript/Node.js (MemoryClient + Memory OSS)client/node.md
    Python vs TypeScript differencesclient/differences.md

    Platform References

    Load these on demand for deeper detail:

    TopicFile
    Quickstart (Python, TS, cURL)references/quickstart.md
    SDK guide (all methods, both languages)references/sdk-guide.md
    API reference (endpoints, filters, object schema)references/api-reference.md
    Architecture (pipeline, lifecycle, scoping, performance)references/architecture.md
    Platform features (retrieval, graph, categories, MCP, etc.)references/features.md
    Framework integrations (LangChain, CrewAI, OpenAI Agents, etc.)references/integration-patterns.md
    Use cases & examples (real-world patterns with code)references/use-cases.md

    Related Mem0 Skills

    SkillWhen to useLink
    mem0-cliTerminal commands, scripting, CI/CD, agent tool loopslocal / GitHub
    mem0-vercel-ai-sdkVercel AI SDK provider with automatic memorylocal / GitHub

    Alternatives

    Compare before choosing

    Computed 8462,498

    mem0ai/mem0

    mem0

    Mem0 SDK reference covering Python and TypeScript APIs, memory client methods, configuration, and framework integrations. Use when writing code that calls mem0 APIs, configuring memory providers, or integrating mem0 into an application.

    Computed 9510,869

    Jeffallan/claude-skills

    fastapi-expert

    Use when building high-performance async Python APIs with FastAPI and Pydantic V2. Invoke to create REST endpoints, define Pydantic models, implement authentication flows, set up async SQLAlchemy database operations, add JWT authentication, build WebSocket endpoints, or generate OpenAPI documentation. Trigger terms: FastAPI, Pydantic, async Python, Python API, REST API Python, SQLAlchemy async, JWT authentication, OpenAPI, Swagger Python.

    Computed 9332,606

    K-Dense-AI/scientific-agent-skills

    genomic-intelligence

    Predict regulatory features, gene structure, and expression directly from DNA sequence using Genomic Intelligence's hosted transformer DNA language models — no local GPU or model weights. Six tasks over a REST API and a hosted MCP server (keyless public demo): promoter regions, splice donor/acceptor sites, enhancer activity, chromatin state, sequence-to-expression (log TPM), and de-novo gene annotation, plus a composite find-genes-then-predict-expression workflow. Use when the user has a gene sy

    Computed 9328

    MoizIbnYousaf/marketing-cli

    build-with-exa

    Build applications and agents with Exa's API Platform: search, contents, answer, context, Agent API, monitors, websets, OpenAI-compatible endpoints, and exa-py / exa-js. Use when choosing Exa endpoints, writing Exa API calls, integrating semantic web search or research into products, or debugging Exa request shapes. Load references/ on demand for endpoint details.