docker-cleanup
Skill1 starsChanged 10 days agoMITView on GitHub
Use this skill when the user asks to wipe / empty / clean / reset Docker — typical phrasings include "limpia docker", "deja docker vacío", "borra todas las imágenes docker", "wipe docker", "docker prune todo", "vacía el docker", "reset docker". Performs a complete cleanup — stops and removes every container, removes every image, removes every named volume, removes every custom network, and clears the build cache. Default networks (bridge, host, none) are kept because Docker recreates them automatically. Single-action skill — no intermediate confirmations.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- vladimiracunadev-create/codex-skills-toolkitedited, first seen Sep 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- vladimiracunadev-create/codex-skills-toolkit★ 094% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- bitcoin-custody-auditSkill
- clone-repoSkill
- docker-compose-doctorSkill
- functional-user-flow-testerSkill
- git-pushSkill
- md-lint-fixSkill
- md-to-docSkill
- pre-commit-guardSkill
- preliminary-product-testerSkill
- pre-push-guardSkill
- python-deps-pinningSkill
- python-lint-guardSkill
- python-version-controlSkill
- release-evidence-auditorSkill
- repo-coherence-auditSkill
- security-auditSkill
- software-resilience-state-testerSkill
- sync-forkSkill
- nombre-del-skillSkill
- version-bumpSkill
- web-snapSkill
- yaml-controlSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
When invoked, run the prepared script scripts/wipe.sh and report the disk space reclaimed.
- Very specific: line 68
If Docker daemon is not running: the script exits 1 with cannot connect to Docker daemon.
- Very specific: line 69
If a volume is in use by an external app the user forgot about: volume in use — the script prints which volume and continues with the rest.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
docker-cleanup
When invoked, run the prepared script scripts/wipe.sh and report the disk space reclaimed. The script is idempotent: re-running it on an already-empty Docker is a no-op.
Scope and permissions
| Script capabilities | shell |
| What it touches | Runs scripts/wipe.sh: stops and removes every container, image, named volume and custom network, and clears the build cache. |
| What it never touches | Leaves the default networks (bridge, host, none) alone and writes nothing outside Docker's own state. |
| Tools removed | WebFetch, WebSearch |
It declares no allowed-tools, deliberately: that field pre-approves tools — skipping the confirmation prompt for the turn that invokes the skill — rather than limiting them. Declaring it here would restrict nothing; it would remove the user's confirmation. disallowed-tools does remove tools from the pool while the skill is active, and that is where the real ceiling lives.
This skill is destructive by design and asks for no intermediate confirmation, so pre-approving its tools would remove the only brake left: the permission prompt.
How to invoke
bash ~/.claude/skills/docker-cleanup/scripts/wipe.shOr on Windows (Git Bash / MINGW):
bash "$(cygpath ~)/.claude/skills/docker-cleanup/scripts/wipe.sh"What the script does, in order
- Stops every running container.
- Removes every container (running or not).
- Removes every image (tagged or dangling).
- Removes every named volume.
- Removes every user-created network.
- Clears the build cache.
- Prints
docker system dfbefore and after.
What it does NOT do
- Does not uninstall Docker.
- Does not touch
bridge/host/nonenetworks (Docker recreates them). - Does not sign out of any registry; credentials stay.
- Does not ask for confirmation — invocation == execution. The user has already decided to wipe when they call this skill.
Failure modes
- If Docker daemon is not running: the script exits 1 with
cannot connect to Docker daemon. Tell the user to start Docker Desktop /systemctl start dockerand retry. - If a volume is in use by an external app the user forgot about:
volume in use— the script prints which volume and continues with the rest.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.