Skip to content
TrustedSkillsbeta
Back to all skills

Docker Best Practices

Checked
josiahsiegel·vlatest·cloud·MIT

Helps with Docker, best practices as part of deploying and managing cloud infrastructure workflows.

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 josiahsiegel/claude-plugin-marketplace --skill docker-best-practices -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

josiahsiegel

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

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

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

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

  • Pinned to a commit: passed

    Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.

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

Scanned
1 file, 604 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

This skill provides best practices for working with Docker, including optimizing container images, securing configurations, and managing containers efficiently. It covers topics like using multi-stage builds, minimizing image size, and ensuring secure defaults in Dockerfiles.

When to use it

  • When creating new Docker images to ensure they follow security and efficiency standards.
  • When troubleshooting performance or security issues with existing Docker setups.
  • When preparing containerized applications for production deployment.
  • When training developers on proper Docker usage within a team.

Key capabilities

  • Guidance on multi-stage builds to reduce image size
  • Recommendations for secure Dockerfile configurations
  • Best practices for managing container lifecycles
  • Tips for optimizing resource usage in containers

Example prompts

  • "How can I reduce the size of my Docker image?"
  • "What are the best practices for securing a Docker container?"
  • "Can you review this Dockerfile and suggest improvements?"

Tips & gotchas

  • Ensure your base images are up to date with security patches.
  • Avoid using RUN commands that install unnecessary packages, as they increase image size and potential attack surfaces.