memory management

v1.0.0

A practical memory management system for OpenClaw: importance scoring, time-decay cleanup, write triggers, hybrid retrieval, and daily maintenance workflow.

0· 94·0 current·0 all-time
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
The name/description say this is a memory management workflow and the SKILL.md only asks the agent to read, write, migrate, and delete files under the suggested workspace (~/.openclaw/workspace) and to run retrieval calls (memory_search / memory_get). No unrelated credentials, binaries, or installs are required.
Instruction Scope
Instructions explicitly direct scanning, migrating, and deleting memory/*.md files older than 30 days and writing to MEMORY.md / topic files. This is consistent with the stated purpose, but it is destructive behavior (deletions/migrations) so users should be aware and back up data before enabling automated maintenance. The skill also assumes a memorySearch capability exists but doesn't include setup steps in this file (it references a related 'memory-setup' skill).
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by an installer. Lowest install risk.
Credentials
The skill requires no environment variables or credentials, which is proportionate. One nuance: it depends on a working memorySearch retrieval backend (vector/FTS) which may itself require configuration or credentials; those are not declared here (the README references a 'memory-setup' skill).
Persistence & Privilege
always:false (normal). The skill suggests scheduling autonomous daily maintenance (cron payload that triggers an agentTurn). Autonomous invocation plus file-deletion behavior increases operational risk if misconfigured, but autonomous invocation itself is the platform default and not a contradiction here.
Assessment
This skill is internally consistent and does what it says: it will read, write, migrate, and delete files in your OpenClaw workspace (e.g., ~/.openclaw/workspace). Before enabling automated or scheduled maintenance: back up your workspace, confirm how your memorySearch backend is configured (the skill references memorySearch but does not provision it), test the workflow on a copy, and review the manual trigger phrases so accidental user messages don't persist or promote deletion. If you want tighter control, run daily maintenance manually or restrict autonomous agent actions until you’re confident with behavior.

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

latestvk9796aebxqn9j7wpfa5wnhrhwn839966

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🧠 Clawdis
OSLinux · macOS · Windows

Comments