How do I install the Dockerfile skill?

Run npx skillmds@latest add paulasilvatech/dockerfile in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Dockerfile skill do?

Use when editing tracked Backstage, agent, MCP, or Golden Path Dockerfiles. It is listed under AI & ML on SkillMD.

Is Dockerfile safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dockerfile?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dockerfile free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dockerfile?

paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dockerfile by paulasilvatech — Agent Skill

Name: Dockerfile
Author: paulasilvatech

File contents

Dockerfiles

Conventions

Pin base images to an explicit supported version; production Dockerfiles must not use latest.
Use multi-stage builds so compilers, caches, tests, and development dependencies stay out of the runtime image.
Copy dependency manifests before source to preserve cacheability and use the package manager matching the lockfile.
Run the final process as a non-root user with only required files and writable directories.
Keep credentials out of ARG, ENV, layers, build context, and package-manager configuration; use build secrets only in approved CI.
Use exec-form entrypoints, propagate termination signals, and expose only documented service ports.
Minimize packages, remove caches in the same layer, and keep runtime versions aligned with local manifests.
Keep health behavior consistent with Compose and Kubernetes probes rather than adding a conflicting endpoint.

Verification

The intended target builds from a clean context.
Image inspection confirms the non-root user, pinned base, and absence of secret material.
The container starts and responds on its documented health endpoint.

Do / Do Not

Do	Do not
Pin base images, minimize build context, and execute as a non-root user.	Bake credentials, mutable bases, or unnecessary build artifacts into an image.
Keep health behavior aligned with deployed probes.	Add a conflicting or artificial health endpoint.

Checklist Before Opening a PR

The change matches this instruction's applyTo scope.
The intended target builds from a clean context.
Image inspection verifies the base, user, and absence of secrets.
The container responds on the documented health endpoint.
No unrelated edits or unresolved placeholders remain.

---name: dockerfiledescription: Use when editing tracked Backstage, agent, MCP, or Golden Path Dockerfiles.---# Dockerfiles## Conventions- Pin base images to an explicit supported version; production Dockerfiles must not use `latest`.- Use multi-stage builds so compilers, caches, tests, and development dependencies stay out of the runtime image.- Copy dependency manifests before source to preserve cacheability and use the package manager matching the lockfile.- Run the final process as a non-root user with only required files and writable directories.- Keep credentials out of `ARG`, `ENV`, layers, build context, and package-manager configuration; use build secrets only in approved CI.- Use exec-form entrypoints, propagate termination signals, and expose only documented service ports.- Minimize packages, remove caches in the same layer, and keep runtime versions aligned with local manifests.- Keep health behavior consistent with Compose and Kubernetes probes rather than adding a conflicting endpoint.## Verification- The intended target builds from a clean context.- Image inspection confirms the non-root user, pinned base, and absence of secret material.- The container starts and responds on its documented health endpoint.## Do / Do Not| Do | Do not || --- | --- || Pin base images, minimize build context, and execute as a non-root user. | Bake credentials, mutable bases, or unnecessary build artifacts into an image. || Keep health behavior aligned with deployed probes. | Add a conflicting or artificial health endpoint. |## Checklist Before Opening a PR- [ ] The change matches this instruction's `applyTo` scope.- [ ] The intended target builds from a clean context.- [ ] Image inspection verifies the base, user, and absence of secrets.- [ ] The container responds on the documented health endpoint.- [ ] No unrelated edits or unresolved placeholders remain.

Frequently asked questions

Dockerfile