SKILLEMALL.ai

BD docker-development

Analyse Dockerfiles and Compose files for security, image size, cache and config problems, with CI-ready exit codes. Use when reviewing or optimising a Dockerfile, validating docker-compose, or adding a container lint step.

borghei/Claude-Skills Agent Skills author: borghei 6 files · 2 scripts body ≈ 1 696 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Analyse Dockerfiles and Compose files for security, image size, cache and config problems, with CI-ready exit codes.

As a process D 42/100 · Unfinished process — References files that are not bundled: examples/Dockerfile.sample

AnalyzerDockerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
99
Quality 40%
86
Run on models
none yet
Process rating
D
42/100
Unfinished process
References files that are not bundled: examples/Dockerfile.sample
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration read-dotenv references/docker-best-practices.md:97
    Reads a .env file (negated — the text forbids it)
    - Never COPY .env files or embed secrets in images
    negated

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: examples/Dockerfile.sample

Process rating: all ten parameters 42/100

Will not run. References files that are not bundled: examples/Dockerfile.sample
  • 0Tools and files. 1 referenced file(s) missing: examples/Dockerfile.sample
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1696 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 223: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 2 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.