Docker Cleanup Toolkit
ReviewAudited by ClawScan on May 15, 2026.
Overview
The skill matches its Docker cleanup purpose, but its prune and force options can delete Docker resources, so use them deliberately.
This appears to be a legitimate Docker cleanup helper. Before installing or invoking it, understand that cleanup flags such as `--volumes`, `--all`, and especially `--force` can permanently remove Docker resources; start with analysis/report mode and approve destructive pruning only when intended.
Findings (2)
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.
Running force or full-prune options can remove stopped containers, dangling or unused images, unused volumes, and networks; deleted volume data may be hard or impossible to recover.
The skill directly invokes Docker prune commands, and the `-f` mode bypasses Docker's interactive confirmation when the force option is chosen. This is expected for a cleanup toolkit but can delete local Docker resources.
cmd = ["volume", "prune", "-f"] if force else ["volume", "prune"] ... cmd = ["system", "prune", "-f"] if force else ["system", "prune"]
Run the default analysis or report mode first, review what will be removed, and only use `--force` or full cleanup after explicit user approval and any needed backups.
The skill may fail unexpectedly on systems without Docker or Python available, or an agent may attempt Docker operations without the registry having surfaced that dependency.
The metadata does not declare required binaries, while the skill documentation requires Docker Engine and Python and the script invokes the `docker` CLI. This may reduce upfront environment checking.
Required binaries (all must exist): none; Required binaries (at least one): none
Publisher should declare Docker and Python requirements in metadata; users should confirm they are comfortable granting Docker CLI access before use.