Memory Manager
v1.0.0自动管理 OpenClaw 的记忆系统，包括工作记忆、短期记忆、长期记忆、记忆合并与压缩。 Triggers: memory manager, memory management, 记忆管理，memory compression, memory cleanup
⭐ 0· 88·0 current·0 all-time
by@wyblhl
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (memory management) aligns with the actual code and SKILL.md: the script only reads/writes/archives/deletes files under D:\OpenClaw\workspace and manages tiers (working/short-term/long-term). There are no extraneous credentials, network calls, or unrelated binaries required.
Instruction Scope
SKILL.md and index.js both instruct file operations (merge, cleanup, archive). That's consistent, but SKILL.md promises interactive safeguards ('删除前确认重要性') and backups while the code performs copies/deletes without user confirmation. Usage examples reference require('./skills/memory-manager') which assumes packaging location; ensure the runtime path matches. The behavior is broad file modification within the workspace (deletion and archiving) — expected for this skill but impactful.
Install Mechanism
No install spec; the skill is instruction+script only. Nothing is downloaded from external URLs and no archives are extracted, so install risk is low.
Credentials
The skill requests no environment variables or credentials. All configuration is hard-coded in the script (absolute Windows paths and retention numbers).
Persistence & Privilege
always is false and model invocation is allowed (default). While that is normal, be aware an agent invoking this skill (autonomously or on user trigger) will perform deletions/archives in your workspace. If you allow autonomous runs, the blast radius is the workspace paths the script touches.
Assessment
This skill appears to be what it says: a local file-based memory manager. Before installing or enabling it broadly: 1) Review and (if needed) change the hard-coded paths (they point to D:\OpenClaw\workspace and include a probable typo 'workspace\\workspace' for learning outcomes). 2) Backup your existing memory and conversation folders. 3) Run the script in a sandbox or test workspace to confirm behavior. 4) If you need confirmations before deletes, add interactive checks or a dry-run mode; the current implementation copies then deletes files without prompting. 5) Ensure the runtime location matches the SKILL.md usage (require path). If you cannot inspect/modify the code, avoid granting autonomous invocation because it will modify files in your workspace.Like a lobster shell, security has layers — review code before you run it.
latestvk971pyt534pjjxzaxpjmsf3cms83dhc8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.