container-status

Report Docker container status, health, uptime, and resource usage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PeterSalvato/joinery --skill container-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-status
Source: https://github.com/PeterSalvato/joinery/tree/main/skills/container-status
Command: npx skills add https://github.com/PeterSalvato/joinery --skill container-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose the current state of Docker containers across your environment, providing quick visibility into which containers are running, stopped, unhealthy, along with uptime and resource usage.

Core Features & Use Cases

  • Container State: List all containers with status (running/stopped) and uptime.
  • Health & Resource Insights: Report health status and CPU/memory usage to identify hotspots.
  • Use Case: Ideal for routine health checks in CI pipelines or during incident response to quickly surface problematic containers.

Quick Start

Check the status of all Docker containers and review health, uptime, and resource usage.

Frequently Asked Questions about container-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the health status and uptime of all Docker containers?

To check Docker container health and uptime, you need an environment with Docker CLI access to gather container info and execute health checks. This process reports running or stopped states alongside resource usage to detect unhealthy containers.

What is the best way to monitor Docker container resource usage for troubleshooting?

Monitoring Docker container resource usage involves gathering container info via Docker CLI commands to report CPU and memory consumption. This approach identifies resource hotspots and flags high consumption during incident response or routine checks.

Can I use this for routine container health checks in a CI pipeline?

Yes, you can perform routine container health checks in CI pipelines if the environment has Docker CLI access. It gathers container info and health status to quickly surface problematic containers during automated deployments.

How do I detect unhealthy Docker containers and surface recent errors?

Detecting unhealthy Docker containers requires Docker CLI access to gather health status and momentary logs for recent errors. This surfaces problematic containers by reporting their current state, health, and recent diagnostic logs.

Does monitoring Docker containers with this approach require external dependencies?

Monitoring Docker containers requires no external dependencies, but it does require Docker CLI access. The environment must support Docker CLI commands to gather the necessary container info, health checks, and momentary logs.

Why should I use a diagnostic tool for Docker container status instead of manual commands?

Using a diagnostic tool for Docker container status provides quick visibility into running, stopped, and unhealthy states along with uptime and resource usage. It aggregates health checks and recent errors to identify hotspots faster than manual commands.