Load immediately after an Agent intent. Then call build-agent with the user's request after any required orchestrator-owned prerequisites are ready. Agent Build
复制下面这句话，粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具，它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-agent-builder-6791028f6b81 ，按照其中的说明把「agent-builder」安装到你（当前 AI 工具）中。执行前先告诉我将运行的命令和写入的位置，等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件，由原作者维护。在 GitHub 查看
Use this skill after intent-recognition chooses an agent-anchored design, or
when the conversation already targets an Agent and the user is continuing that
build. Do not rerun intent recognition for routine Agent edits or extensions.
Use build-agent only for Agent artifacts.
For read-only research, use agent-context directly. This includes explaining
an Agent, comparing Agents, inspecting its config or resources, and diagnosing
sessions. Do not call build-agent for these requests. Call build-agent only
when the request creates, changes, tests, or publishes an Agent. Set its
operation to the matching activity for an existing Agent.
For a new Agent request, make the first build-agent call with a faithful copy
of the request as soon as any required orchestrator-owned prerequisites are
ready. Before that call, use ask-user only to choose a supported channel or to
define a workflow or data-table prerequisite that the orchestrator must create.
Only ask about the channel after agent-context with type: "capabilities" shows that the
requested channel is unsupported. Do not collect model, service, tool, topic,
schedule, credential, or other Agent implementation choices first. The embedded
Agent Builder asks those questions through the build-agent call.
When the conversation opens from an existing Agent in the editor and the user
asks to change its configuration or capabilities, that is an agent-anchored
request — target that Agent and call build-agent. Do not reroute to
workflow-builder, and do not spawn a workflow to satisfy a capability change
on the Agent.
agent-context with type: "capabilities" returns every chat channel n8n Agents support, each
with capabilities, useIntegrationWhen, and useNodeToolWhen. It is the
authoritative source the orchestrator can read before building; a channel
absent from its result is unsupported for agents.
When the user asks for a channel that is not supported (e.g. WhatsApp,
Microsoft Teams), do not forward it to the builder as a channel to configure
and do not fake it by adding the platform as an agent tool. Explain the channel
is unsupported for agents, offer the supported alternatives, and ask which to
use — or whether the user explicitly wants that unsupported platform as the
conversation surface, in which case offer the agent-entrypoint workflow
bridge described in Prerequisites (it connects the platform trigger to Message
an Agent; it is not a channel config). Only forward a channel to build-agent
once it is a supported type or the user has chosen an alternative.
Treat message as a faithful handoff of the user's request, not an Agent build
specification authored by you. Forward the user's wording as close to verbatim
as possible. Include only:
The host appends an block with the current user text and pending ask-user answers that have not yet reached Agent Builder. Treat those as the user's decisions for this build call, not as implementation you invented. Still copy user-stated model, channel, and credential choices into message; do not omit them because the host also injected them.
Never infer, invent, expand, recommend, or prescribe implementation details the user did not request, and never present your assumptions as user requirements. In particular, do not choose or tell the builder which model, instructions, tools, tool types, integrations, channels, MCP servers, workflows, skills, tasks, memory, credentials, triggers, schedules, approvals, or test strategy to use.
Do not translate an outcome or named service into a specific implementation. For example, forward "a Slack agent that says hello to me" without turning it into a request for a Slack node tool. Preserve unspecified and ambiguous implementation details so the builder can resolve them with its own guidance and interactive tools.
Apply the confirm-first handoff only to the first handoff of a template kickoff. That kickoff is the opening message that starts the build after a starter template is already written on the agent, before the user has answered. Read that config. Forward the message as a request to confirm those selections. Do not rewrite them into requirements the user stated. Do not tell the builder to finish the build before the user answers.
Forward every other message as the user wrote it. This includes the user's answer and a later request to change one field, on a template agent or on an agent the user built without a template. Do not turn a change request into another confirmation. Do not add tools, tasks, or instructions the user did not ask for. A change to one field updates only that field.
Before the first build-agent call, create prerequisites the builder cannot
create when they must be attached to or used by the Agent:
workflow-builder, then pass the built workflow in workflowContext.data-table-manager
and create the required tables via data-tables. The builder cannot create
tables.List prerequisite names and schemas in message. Let the builder gather the
remaining Agent-specific requirements, including model, credentials,
integrations, and direct tools.
build-agent can return structured requiredArtifacts when the embedded
builder discovers something Instance AI must create:
relationship: "agent-tool", build it, pass it in
workflowContext, and call build-agent again so the builder can attach it.relationship: "agent-entrypoint", build it after the
Agent exists, using the returned agentId. This workflow invokes the Agent;
never pass it in workflowContext, never attach it to the Agent as a tool,
and do not call build-agent again solely to attach it.build-agent again with its name and
schema in message.For an unsupported chat channel, an agent-entrypoint workflow should connect
the platform trigger to Message an Agent, map the incoming message, use a
stable platform conversation/sender identifier as the custom session key, and
send the Agent's text response through the platform. Native Agent channels do
not need this wrapper.
If an older builder only lists missing workflows or tables in builderReply,
handle them the same way based on whether the workflow calls the Agent or is
called by the Agent. Never ask the user to create prerequisites manually.
Address Agents in this conversation with agentRef, a short stable key similar
to a workflow filePath.
agentRef and name.agentRef on later calls. Calls with neither agentRef nor
agentId continue editing the current Agent.createNew: true with a different
agentRef and name.agentId once,
optionally with an agentRef, then prefer the returned agentRef.Naming or renaming the current Agent never silently creates another one.
When the user asks for an Agent that uses other newly built Agents as saved sub-agents:
agentRef before attaching it to the
parent.build-agent for the parent and identify the child by its display name.
The parent builder must discover the saved child and map its name to the
valid stored ID. Do not pass a raw agentId as a user requirement.When the user asks to test, run, publish, activate, make usable, unpublish, or
otherwise change the Agent, forward that intent in message. The builder owns
its internal testing tools; do not conclude testing is unavailable because
those tools do not appear in your toolset.
When the builder needs a user choice, credential, chat channel, or approval, it
surfaces an interactive card in this chat. Do not relay the question yourself;
the build-agent call resumes with the user's answer.
When you send the user to the agent editor, use the labels they see:
Never say Runs tab, Executions tab, Activity History, or Runs Activity History for an agent.