memory-opportunityOpenClaw Memory-OS - Digital immortality service with conversation memory extraction | 数字永生服务与对话记忆自动提取
Install via ClawdBot CLI:
clawdbot install zhenstaff/memory-opportunityGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
${OPENAIPotentially destructive shell commands in tool definitions
rm -rf ~Calls external URL not in known-safe list
https://github.com/ZhenRobotics/openclaw-memory-opportunityAI Analysis
The skill's documentation explicitly states it is 100% local-only with no network calls or external APIs in the current version, and all data collection is manual. The flagged signals appear to be from documentation examples (like mentioning a future OpenAI variable) or user control commands (rm -rf for data deletion), not actual malicious behavior in the skill's execution.
Usage Guide
Loading usage data… refresh in a few seconds.
Scored Apr 19, 2026
Audited Apr 17, 2026 · audit v1.0
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
Enable and configure Moltbot/Clawdbot memory search for persistent context. Use when setting up memory, fixing "goldfish brain," or helping users configure memorySearch in their config. Covers MEMORY.md, daily logs, and vector search setup.
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vibe-coding ready.
Local memory management for agents. Compression detection, auto-snapshots, and semantic search. Use when agents need to detect compression risk before memory loss, save context snapshots, search historical memories, or track memory usage patterns. Never lose context again.
Audit, clean, and optimize Clawdbot's vector memory (LanceDB). Use when memory is bloated with junk, token usage is high from irrelevant auto-recalls, or setting up memory maintenance automation.