Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsDocker Ops Playbook skill
A safe Docker operations assistant for container management, troubleshooting, and risk-aware cleanup.
$5
Docker Ops Playbook skill
Example session with this skill installed
My web-app container is failing its health check and restarting. Can you help me diagnose the logs and fix it? The container name is 'prod-api-v1'.
- Read your context and instructions
- Compiled the docker ops playbook
I will diagnose the health check failure for 'prod-api-v1' by inspecting the current status, logs, and health configuration.
Docker Health Diagnosis: prod-api-v1
1. Operation: Initial Status & Config Inspection
First, we need to see exactly why Docker marks it as unhealthy and what the defined health check is actually doing.
2. Commands
# Check current container status and last 5 health check outputs
docker inspect --format='{{json .State.Health}}' prod-api-v1 | jq
# View the last 50 lines of logs with timestamps
docker logs --tail 50 --timestamps prod-api-v1
3. Explanation
docker inspect: Extracts the specificHealthobject from the container metadata. This shows the exit codes and logs of the internal health check command.docker logs: Provides the application-level stdout/stderr to see if the app is crashing before the health check even runs.
4. Verification
If the Status in the inspect output is unhealthy, look at Log array in the JSON. An exit code of 1 usually indicates the health check command (like curl or a script) failed to reach the service.
5. Safety Note
Do not restart the container until you have captured the logs; if the restart policy is active, logs from the failed instance might be rotated or lost depending on your logging driver.
6. Troubleshooting
If the logs show "Connection Refused," check if the service is listening on the expected port inside the container:
docker exec prod-api-v1 netstat -tulpn
Next steps
- Provide the output of the
docker inspectcommand above. - Confirm if the application requires a specific startup delay before the health check begins.
- Check if the health check command (e.g.,
curl) is actually installed in the container image.
Connects securely to your tools. The creator never sees your data.
About this skill
Docker management often involves trial-and-error commands that risk data loss or system downtime. This skill provides a structured operational framework for managing containers, images, and stacks with a focus on safety and verification. It transforms vague troubleshooting into precise, executable steps.
What it does
- Container Lifecycle Management handles starting, stopping, and renaming containers with pre-operation status checks.
- Log Diagnosis extracts specific error patterns and health check failures to identify root causes of restart loops.
- Volume & Network Audits maps persistent data paths and container-to-container connectivity to prevent configuration drift.
- Compose Orchestration manages multi-container stacks including scaling, rebuilding, and targeted service restarts.
- Risk-Aware Cleanup identifies dangling images and unused volumes while requiring verification before destructive pruning.
How it works
- Inspection starts by querying the current state of the Docker engine or specific resource.
- Operation Planning generates the necessary
dockerordocker composecommands based on the identified state. - Safety Verification provides a "dry-run" or targeted command to prevent broad data loss.
- Execution and Validation delivers the final commands alongside specific checks to confirm the desired state was reached.
Frameworks & tools
Docker Engine, Docker Compose, and standard Linux/Unix CLI utilities for container management.
Why this beats prompting it yourself
Generic prompts often suggest destructive prune commands or broad rm flags without checking for volume persistence. This skill enforces an inspection-first workflow, ensuring you verify resource dependencies and health status before making changes.
Use cases
- Troubleshooting a container that is stuck in a
CrashLoopBackOffor restart cycle. - Safely reclaiming disk space by identifying truly unused images and build caches.
- Mapping complex container networks to resolve service-to-service communication errors.
- Migrating or backing up persistent volumes after verifying mount points.
Known limitations
Does not support Kubernetes/K8s orchestration or cloud-specific container services like ECS/Fargate. Requires manual input of existing resource names or states to avoid inventing system data.
Does not support Kubernetes. Cannot auto-detect environment state without user-provided logs or command output. No support for cloud-specific container services like AWS ECS.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
No special permissions declared or detected