Skip to content
TrustedSkillsbeta
Back to all skills

Dockerfile Validator

Listed
akin-ozer·vlatest·utilities·Apache-2.0

This Dockerfile Validator by akin-ozer checks your Dockerfiles for common errors and best practices, ensuring efficient image builds and security.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add akin-ozer/cc-devops-skills --skill dockerfile-validator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

akin-ozer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No credential access: failed

    Touches credential material in 2 places.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

    What it found

    • devops-skills-plugin/skills/dockerfile-validator/references/docker_best_practices.md:270AWS credentials file
      RUN --mount=type=secret,id=aws,target=/root/.aws/credentials \
    • devops-skills-plugin/skills/dockerfile-validator/references/optimization_guide.md:369npm auth token
      docker build --secret id=npmrc,src=$HOME/.npmrc .

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 2 places.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • devops-skills-plugin/skills/dockerfile-validator/references/docker_best_practices.md:60remote script piped into a shell
      RUN curl -sL https://example.com/script.sh | bash
    • devops-skills-plugin/skills/dockerfile-validator/references/docker_best_practices.md:67remote script piped into a shell
      && curl -sL https://example.com/script.sh | bash

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • Pinned to a commit: passed

    Scanned akin-ozer/cc-devops-skills at 276af751e6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
276af751e6
Manifest
devops-skills-plugin/skills/dockerfile-validator/SKILL.md
Scanned
7 files, 2,058 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The dockerfile-validator skill analyzes Dockerfiles to identify potential issues and ensure best practices are followed. It checks for syntax errors, security vulnerabilities related to image layers, and adherence to common Dockerfile conventions. This helps prevent build failures and improves the overall quality and maintainability of container images.

When to use it

  • Pre-commit Checks: Integrate into a CI/CD pipeline to automatically validate Dockerfiles before merging code changes.
  • Dockerfile Review: Quickly assess existing Dockerfiles for potential problems during code reviews.
  • Learning & Education: Use as a tool to understand and learn best practices for writing effective Dockerfiles.
  • Troubleshooting Build Issues: Diagnose errors encountered during container image builds by identifying problematic lines in the Dockerfile.

Key capabilities

  • Dockerfile syntax validation
  • Image layer security checks
  • Adherence to Dockerfile best practices

Example prompts

  • "Validate this Dockerfile and report any issues: [Dockerfile content]"
  • "Check this Dockerfile for potential security vulnerabilities in the image layers."
  • "Analyze this Dockerfile and suggest improvements based on common Dockerfile conventions."

Tips & gotchas

The skill requires access to the Dockerfile content. Ensure the AI agent has appropriate permissions or file paths to correctly analyze the provided Dockerfile.