Six-Layer Memory

Set up or repair a proactive six-layer memory system for an OpenClaw/Codex workspace. Use when a user wants durable HOT/WARM/COLD/CURATED/CLOUD/AUTO memory,...

This skill appears to implement what it claims. Important things to consider before installing: 1) Cloud sync: if you place a SuperMemory key in memory/auto-extract/.supermemory_key the supermemory_sync script will upload workspace memory files (SESSION-STATE.md, MEMORY.md, daily logs) to https://api.supermemory.ai — only add that key if you trust the external service and you want those files uploaded. 2) AUTO: if you have a ~/.mem0/config.json and the mem0 Python client is available, the scripts will read that config and may send extracted facts to your Mem0 backend; review ~/.mem0/config.json and the mem0 client to ensure it’s configured as you expect. 3) Cron/autonomy: the README suggests cron entries that run every 30 minutes; installing those will cause regular automatic reads and (if configured) uploads — audit the cron jobs you create. 4) Review workspace contents: the scripts will execute other helper scripts in the workspace (e.g., lancedb_sync or transcript import) via subprocess; ensure those helper scripts are trusted. 5) File placement and permissions: the installer sets SESSION-STATE.md and MEMORY.md to 600/644; verify file permissions if multiple users share the host. If you want to proceed, review/modify scripts (especially supermemory_sync.py and mem0_sync.py) to match your privacy and operational requirements, and avoid placing sensitive secrets inside workspace memory files.

Type: OpenClaw Skill Name: six-layer-memory Version: 2.0.1 The 'six-layer-memory' skill is a legitimate tool for managing agent memory across multiple layers, including local files and optional cloud sync. It includes scripts for setup (install_workspace.sh), maintenance (auto_memory_6layer.py), and syncing with external services like SuperMemory (supermemory_sync.py) and Mem0 (mem0_sync.py). All high-risk behaviors, such as external API calls to api.supermemory.ai and cron-based automation, are clearly documented as core features and require explicit user configuration, such as providing an API key in .supermemory_key. The scripts follow reasonable security practices, such as applying restrictive file permissions (chmod 600) to sensitive memory files.