ecloud-mem0-memory-service for Openclaw

Openclaw Skills for ecloud-mem0-memory-service enable cloud-hosted long-term memory management through CLI-driven CRUD, semantic search, and secure setup.

zjial
v1.0.3
Jul 31, 2026
0
637
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install ecloud-mem0-memory-service

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install ecloud-mem0-memory-service using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is ecloud-mem0-memory-service?

ecloud-mem0-memory-service is an Openclaw Skills package for managing persistent, self-hosted-style long-term memory on a mem0 server through memory.js and setup.js.

It replaces local Markdown-based memory handling with centralized cloud memory operations, adding semantic search, memory protection, de-duplication/update handling, user profile support, and full CRUD workflows for saving, listing, retrieving, updating, and deleting memories.

ecloud-mem0-memory-service Use Cases

  • Store stable user facts such as name, age, city, job, preferences, plans, and other personal context.
  • Detect conversational triggers like "my name is...", "I like...", or "what memories do you have about me?" and route them into memory actions.
  • Search for specific user context, such as profession, likes, or prior details, using semantic lookup.
  • List all known memories when the user asks what the assistant remembers.
  • Retrieve a single memory by ID for inspection or debugging.
  • Update or delete individual memories when user information changes.
  • Wipe all memories when a full reset is explicitly requested.
  • Initialize and validate mem0 server credentials before any memory operation.
  • Enforce cloud-backed memory usage in projects that must not rely on local .md memory files.

How ecloud-mem0-memory-service Works

  1. Detect whether the user input contains persistent personal information or a memory-related request.
  2. If the skill is being used for the first time, collect the required configuration values: Base URL, User ID, and API Key.
  3. Run setup.js to validate and persist mem0 connection settings.
  4. Route the request to the correct memory.js command based on intent: save, search, list, get, update, delete, or delete-all.
  5. For saves, submit the user’s original wording unchanged so mem0 can merge or overwrite memory correctly.
  6. For searches and retrievals, use the configured user_id in the filters and respect score thresholds when interpreting results.
  7. On empty or low-confidence results, ask clarifying questions instead of inventing memory content.
  8. On conflicts or updates, confirm before overwriting unless the user has clearly requested a memory update.
  9. Report results naturally without exposing internal script output phrasing.
  10. If configuration is missing or invalid, stop and guide the user through setup before continuing.

ecloud-mem0-memory-service Setup

Prerequisites

  • Node.js available in the current skill environment.
  • memory.js and setup.js located in the same directory as SKILL.md.
  • A reachable mem0 server endpoint.
  • A valid mem0 API key with the m0sk_ prefix.

First-time configuration

  1. Check whether the skill is already configured:
node memory.js check-config
  1. If configuration is missing, collect the following from the user:
  • Base URL, starting with http:// or https://
  • User ID
  • API Key
  1. Apply the configuration:
node setup.js --user-id "YOUR_USER_ID" --api-key "m0sk_xxx" --base-url "http://localhost:8888"
  1. After successful setup, record the configuration in the project rules or agent notes so future sessions know Openclaw Skills memory is already enabled.

Operational rules

  • Do not write user memory into local Markdown files such as MEMORY.md, USER.md, or memory/*.md.
  • All memory actions must go through node memory.js.
  • The skill directory can be used directly; no directory change is required.

Command reference

node memory.js save '<user original text>'
node memory.js search "<query>" [limit]
node memory.js list
node memory.js get <memory_id>
node memory.js update <memory_id> "<new content>"
node memory.js delete <memory_id>
node memory.js delete-all
node memory.js check-config

ecloud-mem0-memory-service Data Schema & Taxonomy

Data model and taxonomy

Openclaw Skills for ecloud-mem0-memory-service centers on mem0-managed cloud memory records tied to a single user identity.

Field Required Purpose
base_url Yes mem0 server endpoint, must begin with http:// or https://
user_id Yes Identifies the current user and scopes search/list operations
api_key Yes mem0 API key with m0sk_ prefix
memory_id For get/update/delete Unique identifier for one memory record
query For search Search text used for semantic retrieval
limit Optional Maximum number of search results, default is 5

Generated or managed artifacts

  • setup.js output: configuration summary confirming successful connection setup.
  • Runtime memory state: stored remotely in mem0, not as local Markdown.
  • Agent/project notes: a short record that the user has configured mem0 memory, including user ID and server address.

Memory operation taxonomy

  • save: create or merge long-term memory from the user’s original wording.
  • search: semantic lookup for a specific fact or preference.
  • list: enumerate all stored memories for the user.
  • get: fetch a single memory by ID.
  • update: overwrite or refine an existing memory by ID.
  • delete: remove one memory by ID.
  • delete-all: clear all memories after explicit confirmation.
  • check-config: validate whether the environment is ready.

ecloud-mem0-memory-service Advanced Features

  • Cloud-backed long-term memory instead of local file storage, ideal for persistent assistants built with Openclaw Skills.
  • Semantic search support for natural-language queries like preferences, identity, and profile facts.
  • Full CRUD lifecycle with save, list, get, update, delete, and bulk delete operations.
  • Memory protection and conflict-aware behavior to reduce accidental overwrites.
  • User profile enrichment, including support for identity details, preferences, and images mentioned in the skill description.
  • Strict routing through memory.js, making behavior deterministic and easy to automate.
  • First-run onboarding flow via setup.js for guided credential collection and validation.
  • Built-in configuration checks to help agents detect readiness before attempting memory operations.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*