container-debugging — Claude Code skill for container debugging
Troubleshoot Docker and Kubernetes issues, from startup failures and crashes to resource limits and network problems.
npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a claude-codeWhat container-debugging does
This skill guides you through diagnosing container problems, including containers that fail to start, apps that crash, resource limits, and connectivity issues. It also covers performance troubleshooting.
Its quick commands include docker ps, docker inspect, docker stats, docker logs, docker exec, and docker top. More detailed material lives in references/: Docker debugging basics, common issues, container optimization, and a debugging checklist. The command checks require Docker CLI access; without it, you cannot run them.
What it helps with
- find why a container will not start
- trace an application crash through container logs
- check a container’s CPU and memory usage
- investigate network problems in a containerized app
Example prompts for the agent
- Find out why the
apicontainer will not start and suggest diagnostic commands. - Inspect the
workercontainer logs and identify a likely cause of the crash. - Show me how to check whether this container is hitting its CPU or memory limits.
How to install container-debugging
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/container-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/container-debugging/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a codex2Manually: put the files in place
.agents/skills/container-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a cursor2Manually: put the files in place
.cursor/skills/container-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts container-debugging2Manually: put the files in place
.github/skills/container-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/container-debuggingManually: put the files in place
.devin/skills/container-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about container-debugging
How do I install container-debugging in Claude Code?
Run npx skills add aj-geddes/useful-ai-prompts --skill container-debugging -a claude-code. The skill file is at ~/.claude/skills/container-debugging/SKILL.md.
What does the container-debugging skill do?
It helps diagnose Docker container and application issues by checking status, logs, processes, and resource usage.
Which Docker commands does the skill use?
The quick-start checks use docker ps, docker inspect, docker stats, docker logs, docker exec, and docker top.
Source text
SKILL.md · MIT
--- name: container-debugging description: > Debug Docker containers and containerized applications. Diagnose deployment issues, container lifecycle problems, and resource constraints. --- # Container Debugging ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Container debugging focuses on issues within Docker/Kubernetes environments including resource constraints, networking, and application runtime problems. ## When to Use - Container won't start - Application crashes in container - Resource limits exceeded - Network connectivity issues - Performance problems in containers ## Quick Start Minimal working example: ```bash # Check container status docker ps -a docker inspect <container-id> docker stats <container-id> # View container logs docker logs <container-id> docker logs --follow <container-id> # Real-time docker logs --tail 100 <container-id> # Last 100 lines # Connect to running container docker exec -it <container-id> /bin/bash docker exec -it <container-id> sh # Inspect container details docker inspect <container-id> | grep -A 5 "State" docker inspect <container-id> | grep -E "Memory|Cpu" # Check container processes docker top <container-id> # View resource usage docker stats <container-id> # Shows: CPU%, Memory usage, Network I/O // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Docker Debugging Basics](references/docker-debugging-basics.md) | Docker Debugging Basics | | [Common Container Issues](references/common-container-issues.md) | Common Container Issues | | [Container Optimization](references/container-optimization.md) | Container Optimization | | [Debugging Checklist](references/debugging-checklist.md) | Debugging Checklist | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
© aj-geddes · MIT · aj-geddes/useful-ai-prompts
