Memory Enhancer

Automatically extracts facts from daily logs to update and maintain structured long-term memory and summaries.

This skill mostly does what it says (read a daily log and update local memory files), but exercise caution before installing: 1) Confirm what permissions context.sessions_spawn grants on your platform — does the spawned sub-agent have unrestricted filesystem or network access? 2) Ask the author to fix the documentation/code mismatch (SKILL.md says OpenRouter; code spawns 'google/gemini-2.5-flash'). 3) Because the code uses hard-coded absolute paths under /home/bosunjung, either run it in a sandboxed account or modify paths to a dedicated workspace to avoid touching other files. 4) Verify you have backups of MEMORY.md and memory/stats before running, and inspect skill-execution.log after tests. 5) Prefer an explicit allowlist: limit the sub-agent's read/write scope to the specific memory directory and confirm it cannot send data externally (or restrict its network access). If you cannot confirm or constrain the sub-agent's permissions, treat this skill as higher risk and avoid deploying it to sensitive environments.

Type: OpenClaw Skill Name: memory-enhancer Version: 1.0.0 The skill extracts structured data from daily logs to maintain a long-term memory system, but it uses hardcoded absolute paths to a specific user's home directory (/home/bosunjung/) in index.js, which is a security anti-pattern. Additionally, it spawns a sub-agent to perform file writes based on the content of daily logs, which introduces a risk of indirect prompt injection if the logs contain instructions designed to manipulate the sub-agent's file operations.