docker-manager
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: docker-manager
description: Manage Docker containers, images, volumes, and networks. Use when: user wants to list/start/stop…
category: devops
runtime: Docker
---
# docker-manager output preview
## PART A: Task fit
- Use case: Manage Docker containers, images, volumes, and networks. Use when: user wants to list/start/stop/restart containers, check logs, pull images, clean up Docker resources, inspect container stats. NOT for: Kubernetes, building Dockerfiles from scratch. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Core Commands / List & Status” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Manage Docker containers, images, volumes, and networks. Use when: user wants to list/start/stop/restart containers, check logs, pull images, clean up Docker resources, inspect container stats. NOT for: Kubernetes, building Dockerfiles from scratch. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “When to Use / Core Commands / List & Status” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “When to Use / Core Commands / List & Status”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: docker-manager
description: Manage Docker containers, images, volumes, and networks. Use when: user wants to list/start/stop…
category: devops
source: tomevault-io/skills-registry
---
# docker-manager
## When to use
- Manage Docker containers, images, volumes, and networks. Use when: user wants to list/start/stop/restart containers, c…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / Core Commands / List & Status” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "docker-manager" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Core Commands / List & Status
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Docker Manager Skill
Manage Docker containers, images, and infrastructure directly from chat.
When to Use
✅ USE this skill when:
- "Show me running containers"
- "Restart the nginx container"
- "Check logs for my app"
- "How much memory is docker using?"
- "Remove unused images"
- "What ports are exposed?"
- "Pull the latest postgres image"
Core Commands
List & Status
# All containers (running + stopped)
docker ps -a --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
# Container resource usage (live)
docker stats --no-stream --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}"
# Disk usage summary
docker system df
Container Control
docker start <name>
docker stop <name>
docker restart <name>
docker rm <name> # remove stopped container
docker rm -f <name> # force remove running container
Logs
docker logs <name> --tail 100
docker logs <name> --tail 50 --follow # live tail
docker logs <name> --since 1h # last 1 hour
Images
docker images --format "table {{.Repository}}\t{{.Tag}}\t{{.Size}}"
docker pull <image>:<tag>
docker rmi <image>
docker image prune -f # remove dangling images
Cleanup
docker system prune -f # remove stopped containers + dangling images
docker system prune -af # aggressive: remove ALL unused images too
docker volume prune -f # remove unused volumes
Inspect
docker inspect <name>
docker exec -it <name> sh # shell into container
docker exec <name> <command> # run command in container
Networks
docker network ls
docker network inspect <name>
Response Format
When listing containers, always show: Name, Status, Image, Ports in a clean table. When showing logs, show the last 50 lines by default unless asked for more. When cleaning up, always show what was removed and how much space was freed.
Safety Rules
- NEVER remove volumes without explicit confirmation
- NEVER remove running containers unless asked to force-remove
- ALWAYS confirm before
system prune -afas it removes all unused images - Show container names, not just IDs
Source: amirtechai/xclaw — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review