openclaw-memory-canonical
v4.5.5Lightweight file-based memory system for single-user AI agents. Uses markdown files only: HOT/WARM/COLD/BUFFER plus SCRATCH learnings, with tiered loading, W...
⭐ 0· 40·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (file-based memory: HOT/WARM/COLD/BUFFER/SCRATCH) match the provided instructions and scripts. The files and behaviors (atomic write, archiver, health checks, tiered loading) are coherent with a local single-user memory system.
Instruction Scope
SKILL.md directs the agent to read and operate on specific memory files (MEMORY.md, memory/working-buffer.md, .learnings/*, episodic/ etc.) which is expected. However, the included scripts reference a hard-coded absolute path (MEMORY_DIR="/home/irtual/.openclaw/workspace/memory"). The archiver and atomic-write scripts perform move and rename operations that will modify files under that path. Running these scripts unmodified could move or modify files unexpectedly if that path exists on the host or if the user's memory lives elsewhere. Recommend reviewing and adjusting MEMORY_DIR and testing in a sandbox.
Install Mechanism
No install spec or external downloads. The skill is instruction-only plus three small shell scripts included in the bundle; nothing is fetched from remote URLs or registries.
Credentials
No environment variables, credentials, or external service tokens are requested. The scripts operate locally on disk and do not attempt network access or credential usage.
Persistence & Privilege
always is false and the skill does not request persistent elevated privileges. It does include scripts that alter files under a memory directory (rename/mv), which is appropriate for a local memory manager but should be run with care.
Assessment
This skill appears to do what it claims (a local, file-based memory manager) and contains only small bash scripts. Before installing or running: 1) Inspect the scripts (especially archive-old-episodic.sh) and change MEMORY_DIR to the correct path for your environment — do not run them as-is if /home/irtual exists on your system. 2) Back up your memory directory first (the archiver uses mv which will move files). 3) Test health-check.sh and archive scripts in a sandbox or on a copy of your data to confirm behavior. 4) Note that health-check.sh can exit nonzero and the SKILL.md instructs agents to stop memory-dependent reasoning if checks fail — ensure you understand that flow. If you want, paste the scripts with your intended memory path and I can point out any edits to make them safer for your environment.Like a lobster shell, security has layers — review code before you run it.
latestvk976z9r3tw0ptw7p0tg2kqg5d584cqd2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.