- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-docs -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-docs -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-docs -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-docs -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/docker/skills/tree/HEAD/skills/docker-docs來自發布者
Provide current, cited answers about Docker products from official Docker documentation. Docker ships many products beyond containers, including microVM sandboxes for coding agents, a cloud agent platform, hardened images, model serving, and MCP tooling. Many are new or experimental, and their CLIs change often. Training data is a poor source for them. Search first, fetch the page, and cite it.
Say "Docker Docs" or "the official Docker documentation" in answers, and link
the exact https://docs.docker.com/... page that supports each important
claim.
Activate this skill when:
sbx, cloud sandboxes, DHI, DMR, cagent, Offload, Gordon, or
Docker Home.Do not use this skill when:
docker-project-foundations,
docker-build-strategies, docker-compose-patterns,
docker-sandboxes-lifecycle, docker-sandboxes-network-credentials,
docker-sandboxes-kits, docker-agent-config,
docker-agent-run, docker-agent-deploy, or
docker-destructive-guardrails. Use that skill for the procedure, and use
this one only to check a detail against current docs.Make documentation retrieval your first substantive action. Do it before you answer from memory, read bundled references, inspect local files, or draft a plan.
search_docker_docs
from the docker-docs MCP server. Clients may prefix the tool name with
the server or plugin name. Pass one concise query of 2-8 essential terms
in the message argument.llms.txt and
per-page Markdown from docs.docker.com, as described below.site:docs.docker.com, only when the
first two don't surface a relevant page.A missing search tool is not a setup request. Go straight to the fallback. Don't install, configure, or restart anything to answer an ordinary question. Read mcp-setup.md only when the user explicitly asks to add or troubleshoot the Docker docs MCP server.
sbx policy allow network or
DHI migrate Dockerfile, not full sentences. If results are noisy, narrow
the query. If they're empty, try the product's other name. For example,
search Docker Agent as well as cagent.documents, each with a content excerpt and
metadata.source. Usually source_type is docs with a
docs.docker.com URL. It can also be catalog, which is a
Docker-maintained page such as a DHI image guide on GitHub.metadata.source as Markdown. Don't
cite a page you haven't read.docs.docker.com publishes machine-readable entry points:
https://docs.docker.com/llms.txt is a small Markdown map of the primary
sections, product landing pages, and reference entry points. Fetch it
first to choose a section.https://docs.docker.com/llms-full.txt is a page index of roughly 450 KB.
Each entry has a title, URL:, Markdown: URL, and description. It's an
index, not the page text. Don't load it into context whole. With a shell,
download it to a temporary file and search it. Without a shell, navigate
from llms.txt instead..md to the path
without its trailing slash, or request the canonical URL with
Accept: text/markdown. Check that the response Content-Type is
text/markdown. HTML means the route or header was wrong.DOCS_INDEX="$(mktemp)"
curl -fsS https://docs.docker.com/llms-full.txt -o "$DOCS_INDEX"
grep -i -A3 '^## .*cloud sandbox' "$DOCS_INDEX" | head -40
# Two equivalent ways to fetch https://docs.docker.com/ai/sandboxes/cloud/
curl -fsS https://docs.docker.com/ai/sandboxes/cloud.md
curl -fsS -H 'Accept: text/markdown' https://docs.docker.com/ai/sandboxes/cloud/
rm -f "$DOCS_INDEX"
Links inside Markdown pages are root-relative, like /ai/sandboxes/usage/.
Resolve them against https://docs.docker.com and fetch them as Markdown in
the same way. With a web-fetch tool, request the .md URL directly.
Docker means more than containers. Before you search, identify which product
the user means. Ask if it's ambiguous and changes the answer. A sandbox
question might be about local sbx sandboxes, cloud sandboxes, the Sandboxes
API/SDK, or the Agentic Platform Console. Each has its own docs and different
secret and policy stores. Read product-map.md
when you need a product's aliases or top-level docs section, or when the
user's wording might match more than one product.
docs.docker.com first. Docker-maintained sources
the search tool returns, such as DHI catalog guides, are acceptable. Label
them as such. Use other Docker-owned sites only when Docker Docs links to
them, as with per-language Testcontainers docs.docker-destructive-guardrails describes.docker-project-foundations, docker-build-strategies, and
docker-compose-patterns own containerizing projects, Dockerfiles, and
Compose files.docker-sandboxes-lifecycle, docker-sandboxes-network-credentials, and
docker-sandboxes-kits own sbx workflows. No skill in this catalog owns
sbxenv.yaml environment files beyond their kit references; answer those
from the Docker Docs environment files page.docker-agent-config, docker-agent-run, and docker-agent-deploy own
Docker Agent workflows.docker-destructive-guardrails owns confirmation before destructive Docker
commands.references/product-map.md: Docker products, their aliases, and their
top-level docs sections. Use it to pick the right section to search.references/mcp-setup.md: configure or troubleshoot the Docker docs MCP
server, only when the user asks for that setup.checks/verification.md: manual runbook to confirm the MCP tool and the
llms.txt and Markdown fallback still behave as this skill describes.Use this skill to answer questions about any Docker product from current official Docker documentation instead of memory, even if the user just asks "how do I…", "does Docker support…", "what's the fl
---name: docker-docsdescription: Use this skill to answer questions about any Docker product from current official Docker documentation instead…---# skills/docker-docs/SKILL.md總覽
Use this skill to answer questions about any Docker product from current official Docker documentation instead of memory, even if the user just asks "how do I…", "does Docker support…", "what's the flag for…", or "is this still the right way" about Docker. Covers Docker Desktop, Engine, Build/Buildx/Build Cloud, Compose, Hub, Scout, Docker Hardened Images (DHI), Offload, Testcontainers, Docker Sandboxes (`sbx`, local and cloud sandboxes, Sandboxes API/SDK), Docker Agentic Platform, Docker Agent, MCP Catalog/Toolkit/Gateway, Model Runner, Gordon, and account, admin, security, and billing docs. Searches with the `search_docker_docs` MCP tool when available and otherwise falls back to `docs.docker.com/llms.txt` and per-page Markdown.
常見問題
從發布者下載 skills/docker-docs/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/docker/skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。