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.