BC ContainerLint
Docker & container security anti-pattern analyzer -- detects Dockerfile issues, missing health checks, resource limit gaps, privileged containers, insecure networking, and orchestration anti-patterns
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-privilegescripts/dispatcher.sh:81Privilege escalation / world-writable permissions (string literal in code, not executed)echo " DF Dockerfile Best Practices -- latest tag, ADD vs COPY, chmod 777, stale apt cache"
code literal -
low Dangerous commands
cmd-privilegescripts/patterns.sh:34Privilege escalation / world-writable permissions (string literal in code, not executed; security demo / example)'RUN[[:space:]]+chmod[[:space:]]+777|high|DF-007|chmod 777 grants world-writable permissions inside container|Use least-privilege permissions (e.g., chmod 755 or chmod 644)'
code literaldemo -
low Exfiltration
read-dotenvscripts/patterns.sh:157Reads a .env file (negated — the text forbids it)'COPY[[:space:]]+.*\.env|high|OR-015|Copying .env file into image exposes secrets in image layers|Never copy .env files; inject environment variables at runtime'
negated
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 56/100
- 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
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 54 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2163 tokens
- 100Running it twice. Mutating operations check current state
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
- -34 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 199: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: suspicious
ContainerLint is mostly a local container scanner, but its license handling and optional git-hook setup create enough secret-handling, repository-mutation, and local execution risk to require Review.
LLM: suspicious (high) · VirusTotal: · 29 May 2026