Docker Destructive Guardrails

What it does

The source separates targeted container lifecycle actions from broad pruning, volume removal, cache cleanup and context changes. It also routes Compose and sandbox operations to more specific guidance. The intended output is a concrete explanation of which resources and data an operation affects before an agent acts.

Best for

Developers diagnosing disk usage or container problems who want the agent to identify the actual target and choose a bounded operation. It is behavioral guidance, not a Docker wrapper that technically blocks commands.

Tradeoffs and requirements

Instructions can be ignored or misapplied by an agent, so they do not enforce permissions or recover deleted data. The source includes policy exceptions and references with version-sensitive command details. Inspect those details for the installed Docker version. This review did not delete resources or test the policy against an agent.

Applies to any Docker CLI version. This is a behavioral guardrail skill, not a Dockerfile or Compose authoring skill.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/docker/skills/tree/34969c320b839772a26f3855d3e87cc3d8090da1/skills/docker-destructive-guardrails --skill docker-destructive-guardrails

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

Offline package integrity

A temporary folder-copy check, not an agent installation or runtime safety verdict.

6 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.

Inventory SHA-256: 1f9998019a298db01be40c15ae465cd5ab2663afcbafe5e984c9a2df7199bf0d

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

50/100

50

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

2 text files inspected at this exact repository snapshot. 3 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Inspect the active Docker context and named resources, identify persistent data and other users of shared caches, then explain the intended effect and recovery options. Apply the environment's actual authorization rules before executing an operation.

How to judge the result

Use disposable, labeled fixtures to compare the promised scope with actual affected resources. Verify that unrelated volumes and containers remain intact. Passing a dialogue example would demonstrate only that example, not universal prevention of destructive behavior.