OpenClaw System Optimization

Problems It Addresses

During long-term use, OpenClaw develops two common operational burdens: memory, skills, and core config files may be missing after upgrades, deletion, or abnormal operations, requiring manual inspection; Python caches, logs over 10M, temporary files, and leftover install packages keep consuming disk space and raise troubleshooting cost. This skill turns those checks into a daily automated routine, reducing the need to log into the console and clean up manually.

How It Works And Where It Fits

When triggered by a scheduled task, it first runs file health checks for memory, skills, and core config integrity, and attempts automatic repair when items are missing. It then runs memory optimization cleanup for Python caches, redundant logs larger than 10M, temporary files, and unused install packages. After completion, it sends a structured Feishu notification so the checked items, cleaned items, and execution result can be reviewed. The default recommended cron is 0 0 * * *, meaning 00:00 Beijing time daily; the execution time can also be changed by sending an instruction in the Feishu chat, after which the system validates the expression and returns a confirmation. Note that this skill requires an OpenClaw runtime and an authorized Feishu plugin. It fits routine local OpenClaw health checks, but does not replace backups, security audits, or production incident handling.