agentleFS
amanning3390amanning3390/hermeshub/skills/docker-manager/SKILL.md

docker-manager

Skill48 starsChanged 5 months agoMITView on GitHub

Build, run, and manage Docker containers and images. Use when the user mentions Docker, containers, images, docker-compose, or containerized deployment.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a multi-stage Dockerfile for minimal final image

    line 30
  2. Very specific:

    Create docker-compose.yml with service definitions

    line 40
  3. Distinctive:

    Use .dockerignore to exclude unnecessary files

    line 52
  4. Distinctive:

    Use multi-stage builds to reduce final image size

    line 54
  5. Distinctive:

    Run as non-root user in production

    line 55
  6. Distinctive:

    Use HEALTHCHECK for container health monitoring

    line 56
  7. Distinctive:

    Never store secrets in Dockerfiles or images

    line 59
  8. Distinctive:

    Avoid running as root in production containers

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Docker Manager

Container lifecycle management with production-ready patterns.

When to Use

  • User mentions Docker, containers, images, or Dockerfiles
  • User wants to containerize an application
  • User needs docker-compose orchestration
  • User asks about container debugging or optimization

Procedure

Building Images

  1. Analyze the project to determine base image and dependencies
  2. Create a multi-stage Dockerfile for minimal final image
  3. Build: docker build -t name:tag .
  4. Verify: docker images | grep name

Running Containers

  1. Run: docker run -d --name my-app -p 8080:3000 name:tag
  2. Check logs: docker logs -f my-app
  3. Exec into: docker exec -it my-app /bin/sh

Docker Compose

  1. Create docker-compose.yml with service definitions
  2. Start: docker compose up -d
  3. Monitor: docker compose logs -f
  4. Scale: docker compose up -d --scale web=3

Cleanup

  1. Stop containers: docker stop $(docker ps -q)
  2. Remove containers: docker container prune
  3. Remove images: docker image prune -a
  4. Remove volumes: docker volume prune

Best Practices

  • Use .dockerignore to exclude unnecessary files
  • Pin base image versions (node:20-alpine, not node:latest)
  • Use multi-stage builds to reduce final image size
  • Run as non-root user in production
  • Use HEALTHCHECK for container health monitoring

Pitfalls

  • Never store secrets in Dockerfiles or images
  • Avoid running as root in production containers
  • Watch for large context sizes slowing builds
  • Handle signal propagation for graceful shutdown

Verification

  • Container running: docker ps | grep name
  • Health check passing: docker inspect --format='{{.State.Health}}' name
  • Logs clean: docker logs --tail 50 name

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.