agentsclimarketplace
Sign in

Docker cleanup

Skill batteryshark/skill-tap/skills/utilities/docker-cleanup

Survey and safely reclaim Docker disk usage with category-specific confirmation, export options, and platform-aware virtual disk handling.From its SKILL.md

Install
npx -y skills add batteryshark/skill-tap --skill docker-cleanup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.1 KB, 188 tokens by cl100k_base, as published. Nobody here has run it

Clean Up Docker Safely

  1. Run bin/docker-cleanup survey and record Docker's total/reclaimable space plus stopped containers, dangling images, unused volumes, and build cache separately.
  2. Read references/cleanup-policy.md. Offer export/inspection for containers or images whose purpose is unclear.
  3. Obtain category-specific approval. Never infer approval for volumes, docker system prune -a, or deletion from a general request to free space.
  4. Run only approved prune commands and repeat the survey.
  5. On Windows/WSL, compact the Docker VHDX only after pruning, a clean WSL shutdown, explicit elevation, and discovery of the actual disk path. On macOS, use Docker Desktop's supported reclaim behavior for the installed version.

Use agents/cleanup-reviewer.md when persistent data or an unfamiliar environment is involved.

What ships with it: 4 files

2.6 KB alongside SKILL.md, 2 of them executable

agents/

bin/

references/

scripts/

Gives 0 of the 12 instructions most containers cloud skills give in 188 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • Run containers as a non-root userin 66 of 607, across 46 files
  • Use multi-stage buildsin 53 of 607, across 44 files
  • Use Promise.all for independent operationsin 47 of 607, across 13 files
  • Import directly instead of barrel filesin 46 of 607, across 12 files
  • Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • Create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • Copy dependency files before source codein 36 of 607, across 23 files
  • Authenticate server actions like API routesin 35 of 607, across 7 files
  • Use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • run the docker-cleanup survey
  • record Docker space and reclaimable items separately
  • read the cleanup policy
  • offer export for unclear containers or images
  • obtain category-specific approval
  • run only approved prune commands

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.