agentleFS
Sign inStart free
ofershapofershap/mcp-server-docker/skills/docker-management/SKILL.md

docker-management

Skill4 starsChanged 9 months agoMITView on GitHub

Manage Docker containers and images via MCP. Use when the user asks to docker ps, tail container logs, restart a service, exec into a container, check CPU/memory stats, or clean up images on the local host.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Sw1zero/claude-skills★ 0same name

    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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Use this skill when you need to manage Docker containers, inspect logs, run commands inside containers, or check resource usage.

    line 8
  2. Very specific:

    Start with list_containers to see what's running

    line 27
  3. Distinctive:

    Use container names or IDs from the list for all other operations

    line 28
  4. Very specific:

    Use container_stats to check resource usage when diagnosing performance issues

    line 30
  5. Distinctive:

    Always confirm before stopping or removing containers

    line 48
  6. Distinctive:

    Never remove containers in production without explicit user approval

    line 49
  7. Very specific:

    Check container_stats before restarting to understand if the issue is resource-related

    line 50

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Docker Management via MCP

Use this skill when you need to manage Docker containers, inspect logs, run commands inside containers, or check resource usage.

Available Tools

ToolWhat it does
list_containersList running (or all) containers with status, ports, image
container_logsGet recent logs from a container
start_containerStart a stopped container
stop_containerStop a running container
restart_containerRestart a container
remove_containerRemove a container (optional force)
exec_commandExecute a command inside a running container
container_statsGet live CPU, memory, and network stats
list_imagesList all Docker images on the host
remove_imageRemove a Docker image

Workflow

  1. Start with list_containers to see what's running
  2. Use container names or IDs from the list for all other operations
  3. For debugging: container_logs first, then exec_command to investigate
  4. Use container_stats to check resource usage when diagnosing performance issues

Key Patterns

  • list_containers shows only running containers by default; pass all: true for stopped ones too
  • container_logs returns the last N lines; pass tail to control how many
  • exec_command runs inside a running container; the container must be started first
  • remove_container with force: true stops and removes in one step

Error Scenarios

  • Cannot connect to Docker: Docker Desktop/daemon not running or MCP lacks socket permissions
  • Container not found: run list_containers with all: true for stopped IDs/names
  • exec_command fails: container must be running; shell may not exist in minimal images
  • Empty logs: container just started or logging driver differs; increase tail or check app stdout

Safety

  • Always confirm before stopping or removing containers
  • Never remove containers in production without explicit user approval
  • Check container_stats before restarting to understand if the issue is resource-related

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free