ClawHub

Atomic Memory Manager

v1.0.0-alpha

Recall and write workspace memory for OpenClaw agents using MEMORY.md, memory/YYYY-MM-DD.md, memory_search, and memory_get. Use when the user asks about prio...

⭐ 0· 129·0 current·0 all-time
by@omaression
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the instructions: it explains when to retrieve and when to write workspace memory files (MEMORY.md and memory/YYYY-MM-DD.md) and references memory_search/memory_get. It does not request unrelated binaries, env vars, or config paths.
ℹ
Instruction Scope
Instructions stay within the stated purpose: use memory_search and memory_get for retrieval and write small durable notes to MEMORY.md or daily files. They explicitly avoid secrets unless asked and ask the agent to cite file paths. Note: this is purely procedural (no implementation included) and assumes platform-provided memory_search/memory_get primitives; it also relies on the agent not being asked to store secrets — if a user asks the agent to 'remember' sensitive data, those instructions could cause sensitive data to be written to workspace files.
✓
Install Mechanism
Instruction-only skill with no install spec or downloaded code; nothing is written to disk by the skill itself beyond what the agent is instructed to do at runtime.
✓
Credentials
The skill requests no environment variables, credentials, or config paths — proportional to its goal of managing local workspace memory.
✓
Persistence & Privilege
always:false and user-invocable:true. The skill instructs the agent to write files in the workspace (expected for a memory manager) but does not request global system changes or other skills' configurations.
Assessment
This skill is coherent and low-risk relative to its stated purpose. It is instruction-only, so it won't install code, but if invoked the agent will read and write memory files in your workspace (MEMORY.md and memory/YYYY-MM-DD.md). Before using it: (1) avoid asking the agent to 'remember' secrets (the instructions say 'no secrets unless asked' but will follow user requests), (2) confirm how memory_search/memory_get are implemented on your platform and whether those memory files are backed up or visible to others, and (3) periodically review the MEMORY.md and memory/ files to remove any sensitive or stale entries.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bbsqyxb2avafcts7q7g4kvx833f0w

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments