Docker Extend
Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install tools in docker'. Does: Interactively sets up Dockerfile.user and docker-compose.override.yml so users can add personal tools to their Docker environment without affecting maintainer files or committing user-specific config to git.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Docker Extend when an AI agent needs a reusable SKILL.md workflow for this job: Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install tools in docker'. Does: Interactively sets up Dockerfile.user and docker-compose.override.yml so users can add personal tools to their Docker environment without affecting maintainer files or committing user-specific config to git.
When not to use it
Skip Docker Extend when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/docker-extend # Save SKILL.md to ~/.claude/skills/docker-extend/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/docker-extend/SKILL.md. For a shared project, commit the folder at .claude/skills/docker-extend/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Docker Extend skill for this task: Use Docker Extend when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Docker Extend
Sets up personal Docker tool customization using the project's gitignored override pattern. Your `Dockerfile.user` and `docker-compose.override.yml` are yours — never committed to git.
## Step 1: Detect Context
Determine if the user is in dev (source build) or deploy (GHCR) mode:
!`if [ -f docker-compose.yml ] && grep -q 'build: \.' docker-compose.yml 2>/dev/null; then echo "DEV_MODE: Building from source (root docker-compose.yml)"; elif [ -f deploy/docker-compose.yml ]; then echo "DEPLOY_MODE: Using GHCR image (deploy/docker-compose.yml)"; else echo "UNKNOWN_MODE: No docker-compose.yml found in root or deploy/"; fi`
**Decision:** - `DEV_MODE` → work with `Dockerfile.user` + `docker-compose.override.yml` (repo root) - `DEPLOY_MODE` → work with `deploy/Dockerfile.user` + `deploy/docker-compose.override.yml` - `UNKNOWN_MODE` → ask the user which directory their `docker-compose.yml` lives in before proceeding
## Step 2: Check Current State
**DEV_MODE — check root files:**
!`echo "=== Dockerfile.user ===" && (cat Dockerfile.user 2>/dev/null || echo "(not found — will create from example)") && echo "" && echo "=== docker-compose.override.yml ===" && (cat docker-compose.override.yml 2>/dev/null || echo "(not found — will create from example)")`
**DEPLOY_MODE — check deploy/ files:**
!`echo "=== deploy/Dockerfile.user ===" && (cat deploy/Dockerfile.user 2>/dev/null || echo "(not found — will create from example)") && echo "" && echo "=== deploy/docker-compose.override.yml ===" && (cat deploy/docker-compose.override.yml 2>/dev/null || echo "(not found — will create from example)")`
**If both files already exist:** Skip to Step 4 (add tools). **If files are missing:** Proceed to Step 3 (copy from examples). **If example files are missing too:** Tell the user the project hasn't added the example files yet and to check with the maintainers or the docs.
## Step 3: Copy Example Files
Run only the copy commands for whichever files are missing. Do NOT overwrite existing files.
**DEV_MODE:**
```bash # Only if Dockerfile.user does not exist: cp Dockerfile.user.example Dockerfile.user
# Only if docker-compose.override.yml does not exist: cp docker-compose.override.example.yml docker-compose.override.yml ```
**DEPLOY_MODE:**
```bash # Only if deploy/Dockerfile.user does not exist: cp deploy/Dockerfile.user.example deploy/Dockerfile.user
# Only if deploy/docker-compose.override.yml does not exist: cp deploy/docker-compose.override.example.yml deploy/docker-compose.override.yml ```
After running the copy commands, confirm to the user which files were created.
## Step 4: Add Tools
Parse `$ARGUMENTS` for tool names (space-separated, e.g., `vim ripgrep jq`).
**If tools were specified:** Edit the appropriate `Dockerfile.user` to add (or uncomment) the `RUN apt-get install` block with the requested packages. Use the Edit tool — do not rewrite the entire file.
The block to add/modify: ```dockerfile RUN apt-get update && apt-get install -y --no-install-recommends \ <tool1> \ <tool2> \ && rm -rf /var/lib/apt/lists/* ```
**If no tools were specified:** Show the user the file and ask which tools they want to add. Then edit the file accordingly.
## Step 5: Rebuild
Show the user the rebuild command for their context. Do NOT run it automatically.
**DEV_MODE:** ```bash docker compose build && docker compose up -d ```
**DEPLOY_MODE:** ```bash cd deploy && docker compose build && docker compose up -d ```
## Summary
Tell the user: 1. Which files were created (if any) 2. Which tools were added to `Dockerfile.user` (if any) 3. The rebuild command to run when ready 4. A reminder that `Dockerfile.user` and `docker-compose.override.yml` are gitignored — they're personal and won't be committed
Intended uses
- Use Docker Extend when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.