adk-architecture

Explains how the ADK runtime fits together: the node and graph execution model, Context and Event flow, checkpoint and resume, tracing, and the rules governing the public API surface. Use when answering "how does X work" about ADK internals, tracing where an event or a piece of state comes from, deciding where a new capability belongs, reviewing a change to BaseNode, Workflow, Runner, Agent, Event or Context, working out why a node re-ran or stayed waiting after a resume, or judging whether a change breaks the public API. Don't use for assembling an agent from existing pieces (use adk-agent-builder), diagnosing one failing run or test (use adk-debug), or formatting and naming conventions (use adk-style).

跳到安装

仓库: google/adk-python
最近来源活动: 2026年8月13日 00:03
检测到的 SKILL.md 语言: 英语
星标: 21,148
分支: 3,843

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/google/adk-python --skill adk-architecture

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

15 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

adk-sample-creator

Creates a new sample agent in the ADK Python repository — the sample directory, its `agent.py`, and its `README.md` — following the conventions the existing samples already use. Use when the user wants to add a sample or example demonstrating a feature or agent pattern (dynamic nodes, fan-out/fan-in, a standalone tool-using agent), asks where a new sample belongs under `contributing/samples/`, or wants an existing sample's README brought up to the standard structure. Don't use for building a real working agent for the user's own project (use `adk-agent-builder`), or for checking whether the Python blocks in a Markdown file run (use `adk-verify-snippets`).

2026-08-14

adk-agent-builder

Builds ADK (Agent Development Kit) Python agents: LLM agents with tools, graph workflows of function and agent nodes, conditional routing, fan-out and join, schema-validated delegation between agents, human-in-the-loop pauses, and pytest coverage for all of it. Use when asked to create an agent or a workflow, add a tool to one, branch or loop between nodes, run steps in parallel, pause for user approval, or test an agent. Don't use for explaining how ADK works internally or designing its core components (use `adk-architecture`), for an agent that already runs but misbehaves (use `adk-debug`), for authoring a sample under `contributing/` (use `adk-sample-creator`), or for naming, typing, and formatting conventions (use `adk-style`).

2026-08-13

adk-debug

Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the `adk run` CLI and the `adk web` dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs, loops, emits raw JSON instead of calling tools, is not discovered by `adk web`, when a sub-agent cannot see the parent conversation, or when you need the LLM request/response, token counts, or logs for a run. Don't use for how ADK is designed internally (use `adk-architecture`), for building a new agent or workflow (use `adk-agent-builder`), for environment or dependency setup failures (use `adk-setup`), or for lint and style nits (use `adk-style`).

2026-08-13

查看这个仓库的全部 Skills

ADK Architecture

The runtime is a graph of nodes. BaseNode is the unit of execution. Workflow is a node that schedules other nodes along declared edges. NodeRunner executes exactly one node. Runner owns the invocation and the session. Agents are nodes too — BaseAgent extends BaseNode.

A node communicates with its parent through a per-execution Context, and with the session through Events it yields. Those are two separate channels: ctx carries the result upward, events carry persistence and streaming.

Read the source before relying on any signature here. These notes drift; the code does not. Paths below are relative to src/google/adk/.

Pick a reference

Question

Reference

What must a node implement? What may it yield? Which config fields exist?

BaseNode

How does the graph schedule nodes, dedup dynamic children, propagate interrupts?

Workflow

How does a caller start an invocation?

Runner

What is Agent, and which methods do I call on it?

Agent

I am subclassing an agent — what do I override?

BaseAgent

What is on an Event, and what may I assume about its lifetime?

Event

What does a node read and write on ctx?

Context

Who creates the child Context, stamps events, retries, catches errors?

NodeRunner

Why are Runner, NodeRunner and Workflow three separate things?

Runner roles

How does a human-in-the-loop pause and resume work for one node?

Checkpoint and resume

How does a whole workflow survive a pause, and what does is_resumable change?

Workflow resumability

How are spans created, and what attributes do they carry?

Observability

Why does the model not see the raw event log?

LLM context orchestration

Is this change a breaking change? Where does a new export belong?

API principles

Where the code lives

Concept

Module

BaseNode, START

workflow/_base_node.py

Workflow, _LoopState

workflow/_workflow.py

Graph, edge compilation

workflow/_graph.py

NodeRunner

workflow/_node_runner.py

DynamicNodeScheduler

workflow/_dynamic_node_scheduler.py

ReplayManager (resume scan)

workflow/utils/_replay_manager.py

NodeInterruptedError, NodeTimeoutError

workflow/_errors.py

Context, ctx.run_node()

agents/context.py

ReadonlyContext

agents/readonly_context.py

InvocationContext

agents/invocation_context.py

BaseAgent, LlmAgent (aliased Agent)

agents/base_agent.py, agents/llm_agent.py

Event, NodeInfo

events/event.py

EventActions

events/event_actions.py

Branch paths (parent.child@1)

events/_branch_path.py

Node paths (wf@1/child@2)

events/_node_path_builder.py

Runner, InMemoryRunner

runners.py

Node spans, TelemetryContext

Everything under workflow/ is a leading-underscore module. Treat those names as internal — they can change without a major version bump, so a change there is not automatically a breaking change.