open-memory-system
v1.0.0三层记忆系统 — Working/Short-Term/Long-Term Memory 管理。支持自动偏好记忆、实体记忆、事件记录、L2自动提炼、Hook自动触发、Cron定期整理。用于记忆用户偏好、跨会话积累知识、自动化记忆管理。
⭐ 0· 151·0 current·1 all-time
byJochen@jochenyang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description promise a local memory system and the included scripts and hooks exclusively implement file-based memory operations (working/short-term/long-term), L2 distillation, and cron/hook wiring — these requirements align with the stated purpose.
Instruction Scope
Runtime instructions and hook code read and write files in the agent workspace (MEMORY.md, .learnings, memory/*). This is expected for a memory manager, but hooks will automatically read .learnings and MEMORY.md from the workspace when deployed, so you should ensure those directories/files do not contain secrets you don't want the skill to ingest.
Install Mechanism
No remote installers or downloads — the skill is instruction-plus-local-scripts only. The install steps are copy/unzip and creating directories, which is proportionate to the task.
Credentials
The skill declares no required credentials or env vars. Code uses optional environment variables (MEMORY_DIR, OPENCLAW_WORKSPACE) and defaults to a path under /root/.openclaw/workspace/memory; this is reasonable but the default absolute root path and reliance on workspace env vars should be reviewed in your environment. No network credentials are requested.
Persistence & Privilege
always:false (no forced always-on). Hooks are intended to be copied to ~/.openclaw/hooks/ and will run on agent events (session:end, agent:bootstrap) if deployed — autonomous invocation of hooks is expected behavior for this skill but you should be aware hooks will execute automatically once installed.
Assessment
This package appears to do what it says: manage local memory files and provide hooks/crons to auto-save/load and distill short-term items into long-term events. Before installing: (1) inspect the files you’ll allow the hooks to read (MEMORY.md, ~/.openclaw/workspace/.learnings) to ensure they contain no secrets; (2) consider changing the default MEMORY_DIR to a non-root path appropriate for your deployment; (3) avoid passing untrusted input into preference/entity keys (filenames are created directly from keys — this can allow path traversal or odd filenames); (4) review and control deployment of the hook directory (~/.openclaw/hooks/) since hooks will run automatically on agent events; and (5) verify whether any referenced helper (index.py) exists in your environment (cleanup tries to run it if present). Overall the skill is coherent and local-only, but follow these precautions before enabling hooks or crons.Like a lobster shell, security has layers — review code before you run it.
latestvk97a4swa27qcty0y2f9tx8b9qs83fg4m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.