docker-manager

DevOps Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Manage Docker containers, images, volumes, and networks. Use when: user wants to list/start/stop/restart containers, check logs…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to Use”, “Core Commands”, “List & Status”, “Container Control”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name docker-manager directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to Use / Core Commands / List & Status” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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 -af as it removes all unused images
Show container names, not just IDs

Source: amirtechai/xclaw — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: DevOps
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Manual integration
External API key: No requirement detected
Detected OS requirements: Docker
Runtime requirements: Docker
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview docker-manager.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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
```bash
# 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
```bash
docker start <name>
docker stop <name>
docker restart <name>
docker rm <name>         # remove stopped container
docker rm -f <name>      # force remove running container
```

### Logs
```bash
docker logs <name> --tail 100
docker logs <name> --tail 50 --follow   # live tail
docker logs <name> --since 1h           # last 1 hour
```

### Images
```bash
docker images --format "table {{.Repository}}\t{{.Tag}}\t{{.Size}}"
docker pull <image>:<tag>
docker rmi <image>
docker image prune -f    # remove dangling images
```

### Cleanup
```bash
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
```bash
docker inspect <name>
docker exec -it <name> sh        # shell into container
docker exec <name> <command>     # run command in container
```

### Networks
```bash
docker network ls
docker network inspect <name>
```

## Response Format

When listing containers, always show: Name, Status, Image, Ports in a clean table.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> When to Use → Core Commands → List & Status → Container Control → Logs → Images
terms    -> USE this skill when · Manage Docker containers, images, and infrastructure directly from chat. · When listing containers, always show: Name, Status, Image, Ports in a clean table. · --- > Source: [amirtechai/xclaw](https://github.com/amirtechai/xclaw) — distributed by [TomeVault](https://tomevault.io).
files/cmd -> system prune -af · amirtechai/xclaw · github.com/amirtechai/xclaw
body sha256 -> cda47d3dee11