Scan Docker container logs for errors, crashes, and warnings.
npx skills add https://github.com/dixus/claudeframework --skill healthcheck-dixus
Please help me install this Agent Skill. Skill: healthcheck Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/healthcheck Command: npx skills add https://github.com/dixus/claudeframework --skill healthcheck-dixus
This skill helps developers and ops teams quickly identify health issues in running containers by scanning logs for errors and failures.
Run the healthcheck to verify the health of all running Docker services, or pass a service name to check only that service.
High-intent search queries and answers about installing and using this skill.
To scan Docker container logs for errors, this skill collects recent logs from running services and detects common failure patterns like EXCEPTION, HTTP 500, and OOM events. It then classifies findings into BUG, CONFIG, or EXPECTED categories for quick diagnosis.
Monitoring Docker service health via log scanning involves auto-detecting running Docker Compose services and analyzing their recent logs. This skill surfaces misbehaving containers by matching logs against known failure patterns and generating actionable next steps to restore health.
Detecting OOM kills and restarts in Docker containers is done by scanning recent service logs for specific failure signatures. This skill collects logs across all running containers and identifies OOM events, restarts, and HTTP 500 errors to pinpoint crashing services.
Yes, you can check the health of a single Docker Compose service. While the skill auto-detects and scans all running services by default, you can pass a specific service name to limit log collection and error analysis to only that target container.
Detected Docker log errors are classified into three categories: BUG, CONFIG, or EXPECTED. This classification helps developers quickly understand whether a container failure requires a code fix, a configuration change, or if the logged event is an expected operational behavior.
No external monitoring tools are required to diagnose crashing Docker services. This skill independently collects and scans container logs for errors and crashes, providing a quick health summary and actionable guidance without needing additional monitoring dependencies.
DarkMonkDevRestarts Docker development containers and verifies their health and compilation status.
PromakerDevDiagnose unreachable Promaker sites using status, deployments, logs, and URL health checks.
sumik5Manage Docker containers, images, and Compose environments.
BradliebsMonitor live web apps for console errors, performance regressions, and visual anomalies.
