Dockerfile Slimming logo

Dockerfile Slimming

Community
JayCheng113
dockerfile-slimming

Reduce container image size and build time with multi-stage builds and ordered layer caching.

Overview

PublisherJayCheng113
Repositoryskill-retrieval-mcp
Skill namedockerfile-slimming
Stars
134
Forks
23
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by JayCheng113 on GitHub. Read the source before you install it.

Installation

Install the Dockerfile Slimming AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/JayCheng113/skill-retrieval-mcp/tree/main/tests/e2e/corpus/infrastructure/dockerfile-slimming
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/JayCheng113/skill-retrieval-mcp.git /tmp/skill-retrieval-mcp
mkdir -p .claude/skills
cp -r /tmp/skill-retrieval-mcp/tests/e2e/corpus/infrastructure/dockerfile-slimming .claude/skills/dockerfile-slimming
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dockerfile Slimming in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dockerfile Slimming on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dockerfile Slimming is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Making container images small and builds fast

Order instructions from least to most frequently changing. Copying the whole source tree before installing dependencies invalidates the dependency layer on every source edit, which is why a one-line change can trigger a full reinstall. Copy the manifest, install, then copy the source.

Use a multi-stage build so compilers, headers and package caches stay in the build stage and never reach the final image. Copy only the produced artefact across.

Deleting files in a later layer does not shrink the image, because the earlier layer still carries them. Whatever you want gone must never be written in the layer that ships.

Pin the base image by digest. A floating tag makes builds unreproducible and is the usual explanation for an image that built fine last week and fails today.

Frequently asked questions

What does the Dockerfile Slimming AI skill do?

Reduce container image size and build time with multi-stage builds and ordered layer caching.

Why use Dockerfile Slimming on TypingMind?

Because you install it once and use it with any model. Dockerfile Slimming is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dockerfile Slimming in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/JayCheng113/skill-retrieval-mcp/tree/main/tests/e2e/corpus/infrastructure/dockerfile-slimming. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Dockerfile Slimming?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dockerfile Slimming?

As many as you like. As long as a model supports skills, you can use Dockerfile Slimming with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dockerfile Slimming AI skill free?

Yes. It is published on GitHub by JayCheng113 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇