- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add docker/skills --skill docker-agent-deploy -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add docker/skills --skill docker-agent-deploy -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add docker/skills --skill docker-agent-deploy -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add docker/skills --skill docker-agent-deploy -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/docker/skills/tree/HEAD/skills/docker-agent-deploy来自发布者
This skill owns the integration surface of Docker Agent: making an agent
reachable by other software (docker agent serve), distributing it through
an OCI registry the way container images are distributed (docker agent share), and proving it still behaves after a change (docker agent eval).
It assumes the agent config already exists — see docker-agent-config for
authoring it, and docker-agent-run for interactive/local invocation.
Activate this skill when:
Do not use this skill when:
docker-agent-config.--safety/--sandbox, or aliases — use docker-agent-run.Five server modes, each with its own default loopback listen address — never expose any of them beyond loopback without authentication:
docker agent serve mcp ./agent.yaml --http --listen 127.0.0.1:9090 --auth-token "$TOKEN"
serve mcp defaults to stdio transport (for local clients like Claude
Desktop); pass --http only when you need a network-reachable MCP
endpoint, and set --auth-token whenever you do.
Binding any server flag to a non-loopback address without an auth
token/key is refused; --insecure-no-auth exists to force it and must be
treated as a deliberate, documented exception, never a default.
serve mcp (with --http), serve chat, and serve a2a expose
--safety (strict/balanced/restricted/autonomous); Docker's docs
state it defaults to restricted for these modes when unset. serve api
and serve acp expose no --safety flag at all. Never raise --safety
to autonomous on a network-reachable listener; if a served agent must
approve more, prefer balanced and keep auth enabled.
serve api accepts a directory instead of a single file: every
.yaml/.yml/.hcl in it is exposed under /api/agents. Use
--session-workingdir-root to confine session working directories when
the server is reachable by more than one user.
docker login auth:
docker agent share push ./agent.yaml docker.io/username/my-agent:latest
docker agent share pull docker.io/username/my-agent:latest
instruction_file contents are inlined into the pushed artifact
automatically, so a published agent stays self-contained — you do not need
to bundle the referenced files separately.sub_agents that reference the pushed artifact to a digest
(name@sha256:...) once published, to avoid a per-run registry lookup and
to guarantee the exact config a consumer gets.--force on share pull only when you intend to overwrite a local
copy that already exists; without it, an existing local config is left
untouched.evals/ directory next to the agent config by default;
each eval is one JSON session file capturing a user message, the recorded
tool calls, and an evals object with the scoring criteria./eval slash command in
the TUI to save the session, and edit in relevance/size/assertions
criteria afterward.--judge-model, default anthropic/claude-opus-5),
Size (S/M/L/XL response-length bucket), and Assertions (deterministic
checks; see the complete assertion-type list in references/eval-format.md).
Prefer assertions over relevance when a check can be exact: they need no
judge model and are deterministic, not approximation-prone.ANTHROPIC_API_KEY/OPENAI_API_KEY) are forwarded automatically.
GITHUB_TOKEN/GH_TOKEN are not forwarded automatically (they're
broad host credentials, not model keys) — pass them explicitly with
-e GITHUB_TOKEN when an agent's provider needs one (e.g.
github-copilot).--baseline:
docker agent eval ./agent.yaml --baseline results/2026-08-01-run.json --regression-tolerance 0.05
A previously-passing eval that now fails always gates regardless of
tolerance; cost changes are reported but never gate. A baseline or run
with zero evaluations (e.g. an --only pattern matching nothing) is
rejected rather than reported as passing.--keep-containers plus your runtime's exec to inspect a failed
eval's container; the eval's .db session file holds the full
conversation for offline debugging.--safety value used in the deployment before restarting the
listener — this catches an approval-policy regression before it reaches
traffic. If a rollout must be rolled back, restore the prior config and
safety flag; never restore an unauthenticated listener as a rollback
shortcut.agent.yaml, use docker-agent-config.docker-agent-run.references/eval-format.md — full eval session JSON schema and CLI flag table.references/sources.md — provenance of every rule in this skill.assets/eval-session-example.json — a minimal eval session file to copy and adapt.checks/verification.md — Verification runbook for serving, sharing, and evaluating an agent.Use this skill when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or OpenAI-compatible chat), distributing an agent via an OCI registry with `docker agent share`, or measuring agent qu
---name: docker-agent-deploydescription: Use this skill when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or OpenAI-compatible chat)…---# skills/docker-agent-deploy/SKILL.md概览
Use this skill when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or OpenAI-compatible chat), distributing an agent via an OCI registry with `docker agent share`, or measuring agent quality with `docker agent eval`. Even if the user just says they want to "turn my agent into an MCP server", "let Claude Desktop use my agent", "publish my agent to Docker Hub", "push my agent like an image", or "test my agent in CI", this skill applies. Covers `serve mcp/api/a2a/acp/chat` listen addresses and auth flags, `share push/pull`, eval session JSON format, scoring metrics, and the `--baseline` regression gate.
常见问题
从发布者处下载 skills/docker-agent-deploy/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/docker/skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。