How do I install the Docker Management skill?

Run npx skillmds@latest add ofershap-mcp-server-docker/docker-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Docker Management safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docker Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docker Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docker Management?

ofershap (@ofershap-mcp-server-docker) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docker Management by ofershap-mcp-server-docker

Name: Docker Management
Rating: 4.2 (5 reviews)
Author: ofershap

File contents

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

Tool	What it does
`list_containers`	List running (or all) containers with status, ports, image
`container_logs`	Get recent logs from a container
`start_container`	Start a stopped container
`stop_container`	Stop a running container
`restart_container`	Restart a container
`remove_container`	Remove a container (optional force)
`exec_command`	Execute a command inside a running container
`container_stats`	Get live CPU, memory, and network stats
`list_images`	List all Docker images on the host
`remove_image`	Remove a Docker image

Workflow

Start with list_containers to see what's running
Use container names or IDs from the list for all other operations
For debugging: container_logs first, then exec_command to investigate
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

---name: docker-managementdescription: 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.---# Docker Management via MCPUse this skill when you need to manage Docker containers, inspect logs, run commands inside containers, or check resource usage.## Available Tools| Tool | What it does || ------------------- | ---------------------------------------------------------- || `list_containers` | List running (or all) containers with status, ports, image || `container_logs` | Get recent logs from a container || `start_container` | Start a stopped container || `stop_container` | Stop a running container || `restart_container` | Restart a container || `remove_container` | Remove a container (optional force) || `exec_command` | Execute a command inside a running container || `container_stats` | Get live CPU, memory, and network stats || `list_images` | List all Docker images on the host || `remove_image` | Remove a Docker image |## Workflow1. Start with `list_containers` to see what's running2. Use container names or IDs from the list for all other operations3. For debugging: `container_logs` first, then `exec_command` to investigate4. 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

Frequently asked questions

Docker Management