Better Memory
Analysis
Better Memory mostly matches its stated memory-management purpose, but the reviewed code shows unbounded managed-block markers that could rewrite or remove more workspace memory/rule content than promised.
Findings (3)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
MANAGED_AGENT_BLOCK_START = "" ... MANAGED_MEMORY_BLOCK_START = "" ... pattern = re.compile(re.escape(start) + r".*?" + re.escape(end), re.DOTALL)
The file-editing helper uses delimiter strings to replace or remove managed sections, but the provided source shows empty delimiters. That undermines the stated managed-block boundary for edits to AGENTS.md, MEMORY.md, and HEARTBEAT.md.
"# 1) Catch-up run: every 2 hours" ... "# 2) Daily L1 -> L2 review" ... "# 3) Weekly L2 -> L3 rollup" ... "# 4) Monthly advisory review report"
The skill generates recurring maintenance commands. The artifact shows this as a cron template rather than automatic cron installation, so it is disclosed and user-enabled.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
L1 (native): `memory/YYYY-MM-DD.md` ... L2 (sidecar): `.openclaw-memory-os/l2/{experience,value,standard}.md` ... L3 (native): managed block in `MEMORY.md`The skill intentionally creates persistent raw memories, summaries, and rollups that can be reused across future tasks.
