C 盘空间分析与清理技能。用于扫描 C 盘空间使用情况，识别垃圾文件和大文件，根据用户需求执行安全清理操作。使用场景：(1) 分析 C 盘空间占用，(2) 扫描可清理的垃圾文件，(3) 识别可迁移的大型应用，(4) 执行安全清理操作，(5) 生成空间优化建议

The scripts implement the advertised C: scan and cleanup features, but there are a few red flags you should address before running this on a real system: - Do not run the destructive commands without verifying results: always run with --dry-run first and review the output. The code supports dry-run. - The SKILL.md promises a safety file (references/safety.md) and creation of a restore point before cleaning; those are missing/not implemented. Treat the tool as lacking an automatic restore-point feature. - The cleaner writes logs to a hard-coded user path (C:\Users\18785\...), which is unusual. Inspect and edit the script to use a path based on the current user (USERPROFILE) or a configurable location before running. - The included cleanup guide contains advanced commands (vssadmin delete shadows, docker system prune, wsl --unregister) which are potentially destructive if executed — do not run those commands unless you understand the consequences and have backups. - If you obtained this skill from an unknown source, prefer running it in a sandboxed environment or reviewing/editing the code to remove or fix the hard-coded path and to implement or confirm backup/restore behavior. If you’re not comfortable editing code, do not install/run it on a production machine. What would increase confidence: (1) the author providing the missing references/safety.md, (2) replacing the hard-coded log path with a user-based configurable path, and (3) an explicit implementation (or clearly documented omission) of restore-point/backup behavior.

Type: OpenClaw Skill Name: c-cleaner Version: 1.0.0 The 'c-cleaner' skill bundle is a utility designed for Windows disk space analysis and cleanup. It includes scripts for scanning directory usage (scan_c_drive.py), identifying large files (find_large_files.py), and performing deletions of temporary or cache files (clean_c_drive.py). The skill incorporates several safety mechanisms, including a mandatory dry-run preview, explicit exclusion of critical system directories (e.g., System32), and a requirement for user confirmation before any actual deletion occurs. While clean_c_drive.py contains a hardcoded log path (C:\Users\18785\...), this appears to be a developer oversight rather than a malicious indicator, and no evidence of data exfiltration or unauthorized execution was found.