Debug running Docker containers and Compose services. Use when inspecting container logs, exec-ing into running containers, diagnosing networking issues, checking resource usage, debugging multi-stage builds, troubleshooting health checks, or fixing Compose service dependencies.
Data sourced from ClawHub. View on ClawSkills
Select your agent
Option 1: Install via CLI (recommended)
Recommended (no pre-install needed)
npx clawhub@latest --dir ~/.claude/skills install container-debugOr via clawhub CLI (if already installed)
clawhub --dir ~/.claude/skills install container-debugβ οΈ Requires Node.js 18+. No Node? Use Option 2 below to download the ZIP instead. Install Node.js β
Option 2: Manual install (no Node required)
Download the ZIP, extract it, and place the folder at the path below. Restart your agent to activate.
Install path
~/.claude/skills/container-debug/π‘Extract and place the folder at the path above, then restart your agent.
Category
π»Developer & DevOpsPlatforms
What Container Debug can do for your AI workflow
Running docker containers directly from your Claude conversation
Works across Claude, Cursor, OpenClaw β install once, use everywhere
Trusted by 3,899+ developers worldwide
One-command installation β no complex setup required
Combine with other skills to build powerful multi-step AI workflows
Try these prompts with your AI agent after installing Container Debug
Help me get started with Container Debug
Explains what Container Debug does, walks through the setup, and runs a quick demo based on your current project
Use Container Debug to debug running Docker containers and Compose services
Invokes Container Debug with the right parameters and returns the result directly in the conversation
What can I do with Container Debug in my developer & devops workflow?
Lists the top use cases for Container Debug, with example commands for each scenario
Guides & tutorials for AI skills
Container Debug extends your AI assistant with the ability to debug running Docker containers and Compose services. Use when inspecting container logs, exec-ing into running containers, diagnosing networking issues, checking resource usage, debugging multi-stage builds, troubleshooting health checks, or fixing Compose service dependencies. Rather than leaving your conversation to handle this manually, you can ask your Claude agent directly β and it will take care of the task end-to-end, using Container Debug as its underlying capability.
Container Debug works across Claude, Cursor, OpenClaw through the Model Context Protocol (MCP) β an open standard that lets AI clients share tools and skills without lock-in. Because MCP is platform-agnostic by design, you install Container Debug once and it becomes available across all your AI clients. Whether you're working in Claude for focused sessions or Cursor for integrated workflows, the skill behaves consistently.
To install Container Debug, copy the skill folder to `~/.claude/skills/container-debug/` for use across all your projects, or `.claude/skills/container-debug/` for a single project. Restart Claude and the skill is immediately active β invoke it with `/container-debug` or just describe your goal and the AI will pick it up automatically.
Container Debug has been installed 3,899 times, making it one of the more actively used skills in the Developer & DevOps category. The install rate suggests it solves a real, recurring need rather than a niche edge case. Like all skills on DiscoverAISkills, it is free to install and use. The broader AI skills ecosystem continues to expand as developers contribute new capabilities across categories like developer tools, data analysis, writing, automation, and more.
Place the skill folder at ~/.claude/skills/container-debug/ for personal use (all projects), or .claude/skills/container-debug/ for project-specific use. Restart your AI client, then invoke with /container-debug or let the AI discover it automatically.
Container Debug supports Claude, Cursor, OpenClaw. It integrates seamlessly with these AI platforms to extend their capabilities.
Container Debug is free to install. Check the repository for licensing information.
Debug running Docker containers and Compose services. Use when inspecting container logs, exec-ing into running containers, diagnosing networking issues, checking resource usage, debugging multi-stage builds, troubleshooting health checks, or fixing Compose service dependencies.
Automate my developer & devops tasks using Container Debug
Identifies repetitive steps in your workflow and sets up Container Debug to handle them automatically
MCP vs traditional plugins: what's the difference?
Container Debug is categorized under Developer & DevOps. These skills help AI agents perform specialized tasks in this domain.