Docker Debugger
CheckedTroubleshoot Docker container issues with automated log analysis, error identification, and remediation suggestions from onewave-ai.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add onewave-ai/claude-skills --skill docker-debugger -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
onewave-ai
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned onewave-ai/claude-skills at f317e08649.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- f317e08649
- Manifest
- docker-debugger/SKILL.md
- Scanned
- 1 file, 154 lines
About this skill
What it does
The docker-debugger skill allows you to interact with and debug Docker containers. It can inspect container logs, execute commands within a running container, and troubleshoot issues related to container configuration or runtime behavior. This skill is particularly useful when diagnosing problems in complex application deployments that rely on Docker.
When to use it
- Troubleshooting Application Errors: When an application inside a Docker container isn't working as expected, use this skill to examine logs and run diagnostic commands within the container.
- Debugging Configuration Issues: If you suspect a problem with your
Dockerfileor container configuration, this skill can help you inspect files and settings within the container’s environment. - Investigating Performance Bottlenecks: Use it to profile processes inside a container and identify resource constraints impacting performance.
- Reproducing Bugs: Quickly execute commands and examine logs in a specific container state to reproduce and analyze bugs.
Key capabilities
- Inspect container logs
- Execute commands within running containers
- Troubleshoot container configuration issues
Example prompts
- "Show me the latest 100 lines of logs from the 'web-app' container."
- "Run
ps auxinside the 'database' container." - "What is the current working directory within the 'api' container?"
Tips & gotchas
This skill requires you to have Docker installed and running. Ensure that the AI agent has appropriate permissions to access and interact with your Docker environment.