Auto-compress session memories when context usage exceeds 85%

This skill intends to compress and delete old session memory files and then commit changes to git — that behavior matches the description, but there are several red flags you should consider before installing: - The handler contains a logic bug that makes it return immediately (it checks for both 'message' and 'command' at the same time). Expect it to be non-functional until fixed. - HOOK.md requires node and git, but the registry metadata doesn't list these; the code calls git via execSync. Ensure node/git exist and understand that commits (and any future push) may expose data to configured remotes. - The skill deletes files from ~/.openclaw/workspace/memory (filtered by YYYY-MM-DD.md). Back up that workspace before enabling the hook. Although it writes compressed content to MEMORY.md and attempts a git commit, deletion is destructive unless you have a safe backup or repo history. - There is minor command-execution risk: execSync is used with interpolated workspaceDir and shell commands (cd ${workspaceDir} && git add -A). If workspaceDir can be influenced by untrusted input, that could lead to command injection; prefer safe argument passing or sanitization. - There are several content mismatches (60% vs 85% thresholds, 7 days vs 3 days retention). Ask the author to clarify the intended defaults and update documentation and package metadata to match the code. Recommendations before enabling: 1) Test in a disposable workspace (no sensitive data, no active git remotes) to observe behavior. 2) Back up your memory directory and/or ensure the workspace repo is local-only or has no remote push configured. 3) Fix the event-type logic so the handler triggers correctly (handle message and command events separately), and normalize threshold/retention values across SKILL.md, HOOK.md, package.json and handler.ts. 4) Replace execSync shell interpolation with safe child_process invocation (or at least properly quote/sanitize paths) to reduce injection risk. 5) Ask the publisher to update registry metadata to list required binaries (node/git) and to document whether git push will be performed automatically. If you cannot validate these items, treat the skill as risky and do not enable it on any workspace containing sensitive or production data.

Type: OpenClaw Skill Name: context-shrink Version: 1.0.2 The skill contains a potential shell injection vulnerability in handler.ts, where the workspaceDir variable is used directly in an execSync call without sanitization or quoting. Additionally, the code contains a logical error in its event filtering (checking for both 'message' and 'command' types simultaneously) that effectively prevents the handler from ever executing. There are also inconsistencies between the documentation (HOOK.md) and the code (handler.ts) regarding the context usage threshold (60% vs 85%).