Shared Memory Os

Shared memory governance for multi-agent OpenClaw workspaces — with tiered memory, learnings capture, promotion review, lifecycle management, self-maintainin...

This skill appears to implement the described shared-memory governance features, but review before installing: - Confirm the workspace path assumptions: many scripts use the hard-coded ROOT '/home/zqh2333/.openclaw/workspace'. If your environment differs, the scripts could read/write the wrong location or fail. Consider editing scripts to use a relative or configurable workspace root. - Ensure the required binaries exist: Node is required (node scripts are invoked) and the scripts call the 'openclaw' CLI and, in shell variants, 'jq'. The registry metadata did not declare these dependencies — install or declare them first. - Inspect the cron creation: the scripts will upsert scheduled jobs that run node commands with exec/read tooling. Confirm the exact cron messages/commands, schedules, and that jobs run in the intended 'sessionTarget' (isolated). If you do not want automated recurring runs, do not allow the cron upsert step. - Check for secrets and privacy: the skill explicitly tells agents to harvest learnings into .learnings/ and includes a private-secrets template advising to avoid including secrets in learnings. Still, verify that none of your secret files will be referenced/harvested automatically. - Run manually first: instead of enabling cron, run init-shared-memory-os.js and the reporting scripts manually in a controlled environment to verify behavior and outputs. Given the hard-coded paths and undeclared external tool assumptions, treat this skill as suspicious until you confirm and adapt it to your environment.

Type: OpenClaw Skill Name: shared-memory-os Version: 1.7.2 The skill implements a 'Shared Memory OS' for workspace maintenance but exhibits high-risk behavior by instructing the agent to automatically establish persistence. Specifically, SKILL.md directs the agent to immediately create three recurring cron jobs with 'exec' and 'read' privileges. The scripts (ensure-shared-memory-crons.sh and .js) use the 'openclaw cron' command to schedule these tasks, which execute local Node.js scripts. Furthermore, the entire bundle relies on hardcoded absolute paths (/home/zqh2333/.openclaw/workspace), which is highly irregular for a portable skill and suggests targeting a specific environment. While no clear evidence of data exfiltration was found, the automated setup of persistent execution capabilities warrants a suspicious classification.