docker-pilot

Manage Docker containers, images, volumes, networks, and Compose stacks with risk-classified safety gates.

Updated May 21, 2026
One-click install
npx skills add https://github.com/wahajahmed010/openclaw-skills --skill docker-pilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-pilot
Source: https://github.com/wahajahmed010/openclaw-skills/tree/main/skills/docker-pilot
Command: npx skills add https://github.com/wahajahmed010/openclaw-skills --skill docker-pilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

Docker operations often fail in dangerous ways—stopping critical services, deleting volumes by accident, or losing track of fleet health—leading to downtime and data risk.

Core Features & Use Cases

  • Safety architecture with READ / RISKY / DESTRUCTIVE gates: classifies Docker commands by risk and requires explicit confirmation for irreversible actions.
  • Telegram-friendly fleet status and diagnostics: provides an at-a-glance view of running containers, resources, disk usage, and compose readiness.
  • Operational runbooks for real incidents: step-by-step troubleshooting for crash loops, disk full scenarios, port conflicts, DNS/network problems, and image pull issues.
  • Cleanup playbook and security hardening checklist: safe-to-aggressive cleanup phases with audit-first rules, plus guidance for non-root execution, capability drops, and image scanning.

Quick Start

Ask Docker Pilot to generate a current fleet status and highlight any protected services before you perform any stop or restart action.

Frequently Asked Questions about docker-pilot

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

FAQPage Schema
How do I safely stop and restart Docker containers without causing downtime?

Safely manage Docker containers by using risk classification gates that require explicit confirmation for RISKY or DESTRUCTIVE actions, enforcing protected services to prevent accidental downtime during lifecycle operations.

How do I troubleshoot Docker crash loops and port conflicts?

Troubleshoot Docker crash loops and port conflicts using operational runbooks that provide step-by-step diagnostic workflows for common failure modes, including disk full scenarios, DNS issues, and image pull problems.

What is the best way to monitor Docker container fleet health and resource usage?

Monitor Docker fleet health by generating formatted status diagnostics that display running containers, resource utilization, disk usage, and compose readiness for at-a-glance decision making.

Can I perform Docker security hardening and cleanup without losing data?

Perform Docker security hardening and cleanup safely by applying audit-first rules across safe-to-aggressive phases, ensuring non-root execution, capability drops, and image scanning before removing volumes or images.

Does Docker Compose stack management work with confirmation gates for destructive commands?

Docker Compose stack management integrates confirmation gates that classify operations as READ, RISKY, or DESTRUCTIVE, requiring explicit user confirmation before executing irreversible actions on compose stacks.

Why do my Docker cleanup operations fail and delete volumes unexpectedly?

Docker cleanup operations fail destructively without safety gating; applying audit-first rules and protected-service enforcement prevents accidental volume deletion during aggressive image and container removal phases.