Elite Longterm Memory
PassAudited by ClawScan on May 10, 2026.
Overview
This appears to be a purpose-aligned memory skill, but it intentionally persists agent context, can use external memory providers, and includes a manual command that can delete its vector store.
Install this only if you want your agent to maintain persistent memory across sessions. Review the created memory files, avoid storing secrets, be deliberate before enabling cloud/Mem0 integrations, and do not run the LanceDB delete command unless you intentionally want to reset stored vector memories.
Findings (6)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Old, incorrect, or sensitive memories may be reused later and shape the agent's behavior.
The skill intentionally creates persistent agent memory before replies, so stored context can influence future sessions.
Agent (internal): 1. Write to SESSION-STATE.md → "Decision: Use Tailwind" 2. THEN respond
Review and curate memory files regularly, avoid storing secrets, and remove or correct inaccurate memories.
The agent may update long-term memory without mentioning each update in chat.
The documentation tells the agent to store some memory silently, which reduces visibility into persistent changes.
# Store a decision (SILENT - never announce)
If you install it, consider instructing the agent to summarize memory changes or ask before storing sensitive information.
Private conversation or project context may leave the local machine if cloud memory integrations are enabled.
The Mem0 example shows conversation messages being sent to an external memory provider when that optional integration is configured.
await client.add(messages, { user_id: "user123" });Enable SuperMemory or Mem0 only if you trust the provider, understand retention policies, and avoid sending secrets.
A configured API key may incur costs or expose provider access if mishandled.
The skill requires a provider API key for its memory/search integrations, which is expected but grants access to the user's provider account.
Required env vars: OPENAI_API_KEY
Use scoped or dedicated API keys where possible, monitor usage, and revoke keys if you stop using the skill.
Running the command would delete stored vector memories and could cause loss of recalled context.
The documentation includes a destructive shell command that removes the LanceDB memory directory.
rm -rf ~/.openclaw/memory/lancedb/
Run this only as an intentional reset after backing up any memory data you may need.
Installing or running the package may also install third-party code.
The package can pull an optional external dependency with a version range; this is normal for npm integrations but still part of the supply chain.
"optionalDependencies": { "mem0ai": "^1.0.0" }Install from trusted sources, pin versions if needed, and review dependencies for sensitive environments.