← Back to Skills Marketplace
129
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install openclaw-skill-local-docker-health-check
Description
Inspects container health and suggests fixes for common errors
Usage Guidance
This skill is inconsistent: it promises to inspect real Docker containers but the shipped code uses a hard-coded mock (mock_docker.js) and does not call the Docker CLI or Docker API. If you expect a tool that actually inspects containers on your machine, do not rely on this version. Options:
- Review and modify the code to replace mock_docker.js with real Docker interactions (e.g., use dockerode or call the docker CLI), and ensure any added access (Docker socket or DOCKER_HOST) is intentional and secured.
- If you deploy a version that touches the Docker socket or host files, audit it carefully for data exfiltration and limit the skill's permissions.
- If you only want diagnostics examples or a demo, this skill is harmless, but label it clearly as demo/mock. Proceed with caution if you expected real host inspection.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-skill-local-docker-health-check
Version: 1.0.0
The skill is a diagnostic tool designed to simulate Docker container health checks. It uses hardcoded mock data from 'mock_docker.js' to identify common errors like OOM kills or timeouts and provides suggested fixes. There is no evidence of actual system interaction, network activity, or prompt injection; the logic in 'handler.js' is purely analytical and limited to string matching and report generation.
Capability Assessment
Purpose & Capability
The skill's name/description says it inspects container health, but the package requests no Docker binary, no Docker socket, and no environment variables. The included implementation (mock_docker.js) returns hard-coded container lists and logs rather than querying a real Docker daemon, so it cannot perform the stated runtime task on a real host without modification.
Instruction Scope
SKILL.md describes checking containers and logs and exposes a check_containers command, which is consistent in intent. However the instructions are ambiguous about how container data is obtained at runtime (no mention of docker CLI, Docker API, or required host access), and the shipped handler.js relies on mock_docker.js rather than any real Docker integration.
Install Mechanism
No install spec is present and there are no downloads or external installers, which lowers installation risk. The skill is instruction-only with two small JS files included.
Credentials
The skill declares no required environment variables, credentials, or config paths. The code does not access environment variables or external endpoints. This is proportionate to the actual (mock) implementation, but not to the advertised real-world Docker functionality.
Persistence & Privilege
The skill is not forced-always, does not request elevated or persistent privileges, and does not modify other skills or global agent settings. Autonomous model invocation is allowed but not combined with other privilege escalations.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-skill-local-docker-health-check - After installation, invoke the skill by name or use
/openclaw-skill-local-docker-health-check - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
# Docker Medic
An OpenClaw skill that inspects Docker container health and suggests fixes for common errors.
## Files
| File | Purpose |
|------|---------|
| `skill.md` | OpenClaw skill definition — command interface and metadata |
| `handler.js` | Diagnostic engine — scans containers, matches errors, generates reports |
| `mock_docker.js` | Simulated Docker API for testing without a live daemon |
## Commands
### `check_containers`
Inspects container health using keyword-based log analysis.
**Parameters:**
| Parameter | Required | Description |
|-----------|----------|-------------|
| `name` | No | Specific container to check. Defaults to all containers. |
## How It Works
1. **List containers** — calls `listContainers()` to get all container statuses.
2. **Scan logs** — each container's logs are tested against a set of keyword rules.
3. **Match diagnostics** — matched keywords map to a diagnosis and a specific fix.
4. **Generate output** — returns a text summary, a Markdown status table, and JSON prescriptions.
## Supported Diagnostics
| Keyword Pattern | Diagnosis | Suggested Fix |
|-----------------|-----------|---------------|
| `Timeout` | Connection timeout | Restart container; check network config |
| `OOM` / `exit code 137` | Out of memory | Increase memory limit in compose file |
| `Connection refused` | Port unreachable | Verify dependent service is running |
Adding a new diagnostic is a single entry in the `DIAGNOSTICS` array in `handler.js`.
## Quick Start
```bash
node handler.js
```
## Output Format
- **Summary** — plain text listing each flagged container and its diagnosis.
- **Status Table** — Markdown table of all containers with diagnosis and action.
- **Prescriptions** — JSON array of `{ action, target, reason }` objects.
Metadata
Frequently Asked Questions
What is Docker Medic?
Inspects container health and suggests fixes for common errors. It is an AI Agent Skill for Claude Code / OpenClaw, with 129 downloads so far.
How do I install Docker Medic?
Run "/install openclaw-skill-local-docker-health-check" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Docker Medic free?
Yes, Docker Medic is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Docker Medic support?
Docker Medic is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Docker Medic?
It is built and maintained by Peter Lum (@liverock); the current version is v1.0.0.
More Skills