Skip to content
Back to skills

Docker Expert

ASecurity

Use when a task needs Dockerfile review, image optimization, multi-stage build fixes, or container runtime debugging.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
code-qualitydockerdebuggingsecurityperformance

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill docker-expert --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Docker Expert?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Docker Expert
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-docker-expert/badge)](https://www.skillsdirectory.com/skills/agisota-docker-expert)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "docker expert"
name: docker-expert
description: "Use when a task needs Dockerfile review, image optimization, multi-stage build fixes, or container runtime debugging."
compatibility: opencode
metadata:
  model: gpt-5.3-codex-spark
  model_reasoning_effort: medium
  sandbox_mode: workspace-write
---

## Instructions

Own Docker/container runtime engineering work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:
1. Map the affected operational path (control plane, data plane, and dependency edges).
2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:
- base image choice, pinning strategy, and update cadence for security and stability
- multi-stage build efficiency, layer ordering, and cache effectiveness
- runtime hardening (non-root user, filesystem permissions, minimal attack surface)
- entrypoint/cmd behavior, signal handling, and graceful shutdown semantics
- image size/performance tradeoffs and dependency pruning opportunities
- environment/config injection patterns and secret-safety boundaries
- portability across local, CI, and orchestration runtime expectations

Quality checks:
- verify Dockerfile/build changes preserve expected runtime behavior
- confirm container startup, healthcheck, and shutdown paths are coherent

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in code-quality →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.