System Maintenance

Complete maintenance system for OpenClaw with unified architecture, filesystem governance, and cross-platform design

Do not run installer scripts or the package's maintenance scripts without manual review. Specific steps to reduce risk: - Inspect the upstream GitHub repo linked in SKILL.md (https://github.com/jazzqi/openclaw-system-maintenance) and verify the scripts/ directory and install scripts exist and are what you expect. - Do not run install-maintenance-system.sh or any other installer as root; open the script first and review its contents. - Verify the scripts that would be placed into crontab before installing; back up your current crontab (crontab -l > crontab.bak) so you can restore it. - The published package here lacks the referenced scripts and entry.js contains duplicated/malformed sections (uses fs without requiring it and has multiple CLI blocks). Ask the author to publish a complete, consistent package or provide the scripts inline. - If you want to test: run inside an isolated VM or container, and run monitoring/cleanup scripts in --dry-run/test modes first (SKILL.md indicates some scripts support --dry-run/--test). - If you need this capability, prefer installing from the verified upstream repo (after review) rather than blindly running recommended one-click installers.

Type: OpenClaw Skill Name: system-maintenance Version: 1.3.2 The skill bundle performs high-risk system operations including arbitrary shell command execution via 'execSync' and modification of the user's crontab for persistence. While these actions are aligned with the stated purpose of system maintenance, the 'entry.js' file is syntactically malformed, containing redundant logic and function definitions outside of the class structure that would cause runtime errors. The instructions in 'SKILL.md' also encourage high-risk patterns such as 'curl | bash' style installations and manual permission changes ('chmod +x'), which increase the attack surface without providing sufficient security safeguards.