docker-management
Manage Docker containers, images, and services via MCP. Use when asked to list, start, stop, or debug containers.
Works with
--- name: docker-management description: Manage Docker containers, images, and services via MCP. Use when asked to list, start, stop, or debug containers. license: MIT --- # 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 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 ## 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
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

