Ubuntu WSL System Cleanup
v1.0.0Audit and safely clean Ubuntu 24.04 system junk, caches, logs, temp files, and unused local tool artifacts outside /mnt. Use when the user asks to clean the...
⭐ 0· 16·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (WSL Ubuntu cleanup) match the included scripts and references. Requested actions (apt cache, journald vacuum, tmp cleanup, user caches, orphaned-tool scans) are appropriate for the stated purpose; no unrelated credentials, binaries, or external endpoints are required.
Instruction Scope
Instructions and scripts operate on system paths (/var, /tmp, /root, /root/.cache, /root/.local, /var/lib/apt, journalctl) which is expected for a cleanup tool. They explicitly avoid /mnt and Docker unless requested. Note: scripts assume root-centric paths (/root, /root/.openclaw/workspace); on systems where the primary user is not root (e.g., /home/ubuntu), the instructions may need adjustment and will require appropriate privileges to run.
Install Mechanism
No install spec — instruction-only with bundled shell scripts. Nothing is downloaded or extracted from external URLs, lowering installer risk.
Credentials
No environment variables, credentials, or external config paths are requested. The files accessed are consistent with cleanup tasks (apt caches, journald, /tmp, user caches, pipx/pip/npm locations).
Persistence & Privilege
Skill does not request permanent/always-on presence and allows user invocation. It does require the agent (or user) to run scripts with appropriate filesystem privileges to perform cleanup, which is expected.
Assessment
This skill is coherent with its stated purpose, but it performs destructive filesystem operations (rm -rf, apt-get clean, journal vacuum). Before running: 1) Confirm whether the environment uses /root or a non-root $HOME — the scripts target /root paths. 2) Ensure you (or the agent) run the scripts with the correct privileges and explicit user consent for any extended or Docker cleanup. 3) Back up important data or run a dry-run/listing first (check the reported 'before' output and the scan lists) before allowing deletions. 4) If you want the cleanup to target a non-root user home, modify the script paths or run as that user. If any behavior seems unexpected (e.g., deleting specific caches or removing tool files), ask for a detailed review before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk9747defhn8v5fqrhme8p0edzn84b2b1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.