Claude Skill

docker-operator

Build, run, inspect, and diagnose Docker containers and Compose stacks safely. Use when debugging images, ports, volumes, or container logs.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_docker-operator-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/docker-operator

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Docker Operator

Overview

Operate Docker with least surprise: inspect before restart, prefer Compose files in-repo, avoid destructive prune unless approved.

Common commands

docker ps -a
docker logs --tail 200 <container>
docker compose ps
docker compose logs -f --tail=100
docker image ls
docker inspect <id>

Workflow

Confirm context (compose file path, service name).
Inspect running state and recent logs.
Reproduce the failure with the smallest command.
Change config/code → rebuild only what is needed.
Verify healthchecks / HTTP readiness.

Rules

docker system prune / volume deletes need human-approval.
Do not publish privileged containers unless required and approved.
Never embed secrets in image layers; use env/secrets.

Files (navin)

SKILL.md 1 KB

---
name: docker-operator
description: Build, run, inspect, and diagnose Docker containers and Compose stacks safely. Use when debugging images, ports, volumes, or container logs.
metadata: {"navin":{"emoji":"🐳","category":"devops","requires":{"bins":["docker"]}}}
---

# Docker Operator

## Overview

Operate Docker with least surprise: inspect before restart, prefer Compose files in-repo, avoid destructive prune unless approved.

## Common commands

```bash
docker ps -a
docker logs --tail 200 <container>
docker compose ps
docker compose logs -f --tail=100
docker image ls
docker inspect <id>
```

## Workflow

1. Confirm context (compose file path, service name).
2. Inspect running state and recent logs.
3. Reproduce the failure with the smallest command.
4. Change config/code → rebuild only what is needed.
5. Verify healthchecks / HTTP readiness.

## Rules

- `docker system prune` / volume deletes need `human-approval`.
- Do not publish privileged containers unless required and approved.
- Never embed secrets in image layers; use env/secrets.