Cache Cleanup

PassAudited by ClawScan on May 1, 2026.

Overview

This is a coherent cache-cleanup skill, but it can delete old local OpenClaw/cache files and run on a recurring schedule, so users should review the target paths before enabling it.

Install only if you want old OpenClaw cache, log, browser, sandbox, and project cache files deleted automatically. Check that `/root/.openclaw` is the correct workspace path for your environment, and consider disabling the cron schedule or adding a dry-run/exclusion list if any target directory may contain important data.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Old files in logs, browser cache, canvas, sandbox, temporary OpenClaw files, and project `.cache` directories may be deleted.

Why it was flagged

The script performs irreversible local file and directory deletion. This is purpose-aligned for cache cleanup, but users should notice the destructive authority.

Skill content
find "$dir" -type f -mtime +$days -delete 2>/dev/null ... find "$WORKSPACE/projects" -name ".cache" -type d -mtime +7 -exec rm -rf {} +
Recommendation

Review the listed paths and retention periods before enabling; consider adding a dry-run mode, exclusions, or backups for any directory that may contain important work.

NoteHigh Confidence
ASI10: Rogue Agents
What this means

If scheduled, the cleanup may run every three days without the user manually starting it each time.

Why it was flagged

The skill declares a recurring schedule. This is disclosed and consistent with cache cleanup, but it is a persistence mechanism that can repeat deletion automatically.

Skill content
"cron": "0 2 */3 * *"
Recommendation

Enable the cron schedule only if recurring cleanup is desired; otherwise run `cleanup.sh` manually or remove the schedule.

What this means

A user following the example may configure a non-existent wrapper script or fail to schedule the intended cleanup script.

Why it was flagged

The usage example references `run.sh`, while the supplied files and skill.json use `cleanup.sh`. This is an artifact consistency issue that could confuse installation.

Skill content
cron job add cache-cleanup "0 2 */3 * *" ~/.openclaw/workspace/skills/cache-cleanup/run.sh
Recommendation

Update the documentation to reference `cleanup.sh`, or include and document the `run.sh` wrapper if it is required.