跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 docker-agent-config

Docker Agent Config

在为 Docker Agent (cagent) 创建或编辑 agent.yaml (或.yml/.hcl) 配置文件时使用此技能, 包括定义代理, 模型/ 提供者, 内置或 MCP 工具, 带有 sub_ agents 的多代理团队. 即使用户只是说他们想"与多克一起建立一个AI代理","制作一个编码代理配置","给我的代理添加一个工具",或者"建立一个代理团队",这种技能适用. 覆盖代理属性(模型,指令,工具ets,sub_agents,倒置),模型/提供器部分,内置工具et(文件系统, shell, think,todo,内存,取回),MCP工具et引用,并命名命令.

1106 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在为 Docker Agent (cagent) 创建或编辑 agent.yaml (或.yml/.hcl) 配置文件时使用此技能, 包括定义代理, 模型/ 提供者, 内置或 MCP 工具, 带有 sub_ agents 的多代理团队. 即使用户只是说他们想"与多克一起建立一个AI代理","制作一个编码代理配置","给我的代理添加一个工具",或者"建立一个代理团队",这种技能适用. 覆盖代理属性(模型,指令,工具ets,sub_agents,倒置),模型/提供器部分,内置工具et(文件系统, shell, think,todo,内存,取回),MCP工具et引用,并命名命令.

何时用

这个技能

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Docker Agent Configuration、Overview、When to use this skill、Do not use this skill when、Core guidance、File structure。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/toolsets-and-providers.md、assets/team-agent.yaml、references/sources.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Use this skill when creating or editing an agent.yaml (or .yml/.hcl) configuration file for Docker Agent (cagent), including defining agents, models/providers, built-in or MCP toolsets, multi-agent teams with sub_agents. Even if the user just says they want to "build an AI agent with Docker", "make a coding agent config", "add a tool to my agent", or "set up a team of agents", this skill applies. Covers agent properties (model, instruction, toolsets, sub_agents, fallback), the models/providers sections, built-in toolsets (filesystem, shell, think, todo, memory, fetch), MCP toolset references, and named commands.

Docker Agent ConfigurationOverviewWhen to use this skillDo not use this skill whenCore guidanceFile structureModels and providersToolsetsMulti-agent teamsSafety and hygieneRelated skillsReferences

兼容:Requires the docker-agent CLI plugin (Docker Desktop 4.63+, or standalone via Homebrew/GitHub releases). Verified against docker-agent as shipped with Docker CLI 29.7.2. Config directories still use the legacy `cagent` name (`~/.config/cagent`, `~/.cagent`). · 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
docker-agent-config
description
Use this skill when creating or editing an agent.yaml (or .yml/.hcl) configuration file for Docker Agent (cagent), including defining agents, models/providers, built-in or MCP toolsets, multi-agent teams with sub_agents. Even if the user just says they want to "build an AI agent with Docker", "make a coding agent config", "add a tool to my agent", or "set up a team of agents", this skill applies. Covers agent properties (model, instruction, toolsets, sub_agents, fallback), the models/providers sections, built-in toolsets (filesystem, shell, think, todo, memory, fetch), MCP toolset references, and named commands.
compatibility
Requires the docker-agent CLI plugin (Docker Desktop 4.63+, or standalone via Homebrew/GitHub releases). Verified against docker-agent as shipped with Docker CLI 29.7.2. Config directories still use the legacy `cagent` name (`~/.config/cagent`, `~/.cagent`).
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 3
  • references/toolsets-and-providers.md
  • assets/team-agent.yaml
  • references/sources.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「docker-agent-config」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-80e44c2dbde89297-%E5%B5%8C%E5%85%A5%E4%BB%A3%E7%90%86%E9%85%8D%E7%BD%AE.html
请存为 .cursor/skills/docker-agent-config/SKILL.md 或 .claude/skills/docker-agent-config/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/docker/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/docker/skills' --list

npx skills add 'https://github.com/docker/skills' --skill 'docker-agent-config'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: docker-agent-config description: Use this skill when creating or editing an agent.yaml (or .yml/.hcl) configuration file for Docker Agent (cagent), including defining agents, models/providers, built-in or MCP toolsets, multi-agent teams with sub_agents. Even if the user just says they want to "build an AI agent with Docker", "make a coding agent config", "add a tool to my agent", or "set up a team of agents", this skill applies. Covers agent properties (model, instruction, toolsets, sub_agents, fallback), the models/providers sections, built-in toolsets (filesystem, shell, think, todo, memory, fetch), MCP toolset references, and named commands. license: Apache-2.0 compatibility: Requires the docker-agent CLI plugin (Docker Desktop 4.63+, or standalone via Homebrew/GitHub releases). Verified against docker-agent as shipped with Docker CLI 29.7.2. Config directories still use the legacy `cagent` name (`~/.config/cagent`, `~/.cagent`). --- # Docker Agent Configuration ## Overview Docker Agent (the CLI is `docker agent`, the open-source project is `cagent`) runs AI agents declared in a YAML file instead of application code. This skill owns the `agent.yaml` artifact: the `agents` section (each entry's `model`, `instruction`, and its own `toolsets`/`sub_agents`), the top-level `models`/`providers` sections referenced from agents, and a top-level `commands` group agents can opt into with `use_commands`. It does not cover invoking the CLI or serving/sharing the config — see Related skills. ## When to use this skill Activate this skill when: - The user is creating, editing, or reviewing an `agent.yaml`/`agent.yml`/`agent.hcl` file. - The user wants to add a tool/toolset, an MCP server, or a sub-agent to an agent config. - The user wants to choose or configure a model/provider (OpenAI, Anthropic, Google, Bedrock, Docker Model Runner, custom endpoint) for an agent. - The user wants a multi-agent "team" with a coordinator delegating to specialists. ## Do not use this skill when Do not use this skill when: - The task is about running the CLI (`docker agent run` flags, `--safety`, `--sandbox`, aliases, worktrees) — use `docker-agent-run`. - The task is about exposing an agent as a server (`serve mcp/api/a2a/acp/chat`), distributing it (`share push/pull`), or evaluating it (evaluation sessions, `--baseline` regression gates) — use `docker-agent-deploy`. - The task is about a generic Dockerfile or Compose service unrelated to Docker Agent — use `docker-build-strategies` or `docker-compose-patterns`. ## Core guidance ### File structure - Every config needs at least one agent under top-level `agents:`. The agent named `root`, or the first agent defined, is the entry point that receives user messages. ```yaml agents: root: model: anthropic/claude-sonnet-4-5 description: A coding assistant instruction: | You are an expert developer. Help users write clean, efficient code. Explain your reasoning step by step. toolsets: - type: filesystem - type: shell - type: think ``` - Required agent properties: `model`, `description`, `instruction` (or `instruction_file`). `description` is not decoration — other agents read it to decide whether to delegate to this one, so keep it accurate. - Use `instruction_file` (a relative path, no `..`) instead of an inline `instruction` for long prompts; this keeps diffs focused on behavior, not YAML escaping. `instruction` and `instruction_file` are mutually exclusive. `instruction_file` is not supported for agents loaded from an OCI reference or URL — inline `instruction` there. ### Models and providers - Two ways to set a model: inline `provider/model` shorthand, or a named entry under top-level `models:` referencing a `provider`. Use the named form whenever you need `temperature`, `max_tokens`, `thinking_budget`, or reuse across agents. ```yaml models: claude: provider: anthropic model: claude-sonnet-4-5 max_tokens: 64000 agents: root: model: claude ``` - Built-in provider keys: `openai`, `anthropic`, `google`, `amazon-bedrock`, `dmr` (Docker Model Runner, local, no API key), `ollama` (local). Dozens of additional built-in aliases exist (`mistral`, `groq`, `xai`, `together`, `azure`, `github-copilot`, `openrouter`, ...) — each needs its own `_API_KEY`-style env var; run `docker agent models --all` to see what's resolvable, and `docker agent setup` to register credentials interactively instead of hand-editing env vars. - Never hardcode an API key in `agent.yaml`. Provider credentials come from environment variables (`token_key` for custom providers) or from `~/.config/cagent/.env` written by `docker agent setup`. - Prefer `dmr/` for agents that must run offline or must not send data to a third party; it costs nothing and needs no credential. Use a paid cloud provider only when the task needs it. - Give resilience-critical agents a `fallback` so a provider outage or rate limit does not stop the run: ```yaml agents: root: model: anthropic/claude-sonnet-4-5 fallback: models: [openai/gpt-5, google/gemini-3.5-flash] retries: 2 # per model, for 5xx errors cooldown: 1m # stick with fallback after a 429 ``` - For a self-hosted/OpenAI-compatible endpoint (vLLM, LiteLLM, a corporate gateway), define a `providers:` entry with `base_url` and `token_key` rather than putting the URL inline on every model: ```yaml providers: my_gateway: base_url: https://api.example.com/v1 token_key: MY_API_KEY models: my_model: provider: my_gateway model: gpt-4o ``` ### Toolsets - Built-in toolsets need no external dependency: `filesystem`, `shell`, `think`, `todo`, `tasks`, `memory`, `fetch`, `background-jobs`, `script`, `lsp`, `api`. Add one per list entry: ```yaml toolsets: - type: filesystem - type: shell ``` - If an agent only describes a plan but never executes it, add `type: todo` (or `shell`) — a common symptom of an agent missing the tool it needs to act, not a model problem. - For external tools, prefer an MCP server from Docker's MCP catalog over a bespoke integration — it runs containerized and is reusable across agents: ```yaml toolsets: - type: mcp ref: docker:duckduckgo ``` Local stdio and remote HTTP/SSE MCP servers are also supported; see `references/toolsets-and-providers.md`. - Use `defer: true` on a toolset (MCP or otherwise) to load its tools on-demand instead of at startup, when the agent has many toolsets and startup latency matters. - Set `readonly: true` on an agent to restrict every toolset it uses to read-only tools — use this for reviewer/analysis agents that must not mutate anything. ### Multi-agent teams - A coordinator delegates via `sub_agents: [name, ...]`; listing sub-agents automatically enables the `transfer_task` tool on the parent. ```yaml # Fragment: coder and reviewer are defined separately in the full asset. agents: root: sub_agents: [coder, reviewer] ``` Use `assets/team-agent.yaml` for the complete runnable team, including the reviewer's `readonly: true` restriction. Keep that restriction when adapting the template; a filesystem toolset alone also exposes writes. - `sub_agents` also accepts external OCI references (`myorg/agent:tag`). Pin external references to a digest (`name@sha256:...`) in production configs to skip the per-run registry lookup that a tag incurs. - Use `transfer_task` (via `sub_agents`) for delegation with a clean, isolated result; use a `commands:` entry with an `agent:` field only when you want the user to *become* that agent for the rest of the session. ### Safety and hygiene - Set `redact_secrets: true` on any agent that runs shell/fetch tools against untrusted input. It scrubs recognized secret patterns from tool arguments, outgoing messages, and tool output. This is defense in depth, not a guarantee: arbitrary passwords, tokens, or customer data may go undetected. - Set `max_iterations` on any agent that loops autonomously (default is unlimited) to bound cost and prevent runaway loops; `max_consecutive_tool_calls` (default 5) already guards against identical-call loops. - Keep credentials, tokens, and sensitive customer data out of `instruction`, `instruction_file`, and command prompts, whether literal or interpolated. `${env.VAR}` expands values into prompt text sent to the model; storing a value in an env file does not prevent this disclosure. Use interpolation only for non-sensitive context. - Supply provider credentials through `docker agent setup` or the provider's supported environment variables. For custom providers, `token_key: MY_API_KEY` names the environment variable, not its value; do not interpolate it. Configure tool/MCP credentials through that integration's authentication mechanism, not through prompts or model-supplied tool arguments. Prompts should describe the authenticated capability without containing its secret. Do not ask the agent to read or print credential files or environment values to check authentication. ## Related skills - For running the agent (`docker agent run`, safety modes, sandbox, aliases), use `docker-agent-run`. - For serving, sharing, or evaluating the agent, use `docker-agent-deploy`. ## References - `references/toolsets-and-providers.md` — full built-in toolset list, MCP connection modes, and the provider/env-var table. - `references/sources.md` — provenance of every rule in this skill. ## Assets - `assets/team-agent.yaml` — a runnable multi-agent team template (coordinator + coder + reviewer). ## Checks - Before running an agent, follow `checks/verification.md` to confirm its resolved config, exposed tools, and provider connectivity, then smoke-test it.

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…