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`).

跳到安装查看文件

仓库: google/adk-python
最近来源活动: 2026年10月1日 21:28
检测到的 SKILL.md 语言: 英语
星标: 21,870
分支: 4,182

安装方式

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

用 AI 助手安装

复制这段 Prompt，发给你正在使用的 AI 助手。

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/google/adk-python/tree/main/.agents/skills/adk-debug.

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

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

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

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

检查来源文件

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

文件资源管理器

6 个文件

SKILL.md

来源说明 · 只读预览

name: adk-debug
description: 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`).

# Debugging ADK agents Two entry points. Default to `adk run`: one process, no server, and `--jsonl` output that pipes straight into `grep` or `python3`. Switch to `adk web` when you need the browser UI, a persisted session you can click through, or the trace endpoints that expose the exact LLM request. ## First moves 1. Reproduce headlessly: `adk run --jsonl {agent_dir} "{query}"`. Without `--jsonl`, `adk run` prints only text parts — tool calls and tool errors are invisible. 2. Read the log file. `adk run` writes to `/tmp/agents_log/agent.latest.log` and nothing to the terminal; `adk web` does the opposite. See [logs-and-traces.md](references/logs-and-traces.md). 3. Match the symptom in [failure-modes.md](references/failure-modes.md) before reading source — most reports are one of a handful of known shapes. 4. If the text is fine but the routing is not, dump the events and read `author`, `branch`, `nodeInfo.path`, and `actions` — [event-flow.md](references/event-flow.md). 5. If the model itself misbehaved, read what it actually received from the `call_llm` span rather than guessing from the agent definition — [logs-and-traces.md](references/logs-and-traces.md). ## References - [cli-run.md](references/cli-run.md) — `adk run` flags, the JSONL event shape, multi-turn and human-in-the-loop resume, exit codes, driving a `Runner` from Python. - [web-api.md](references/web-api.md) — starting `adk web`, listing and reading sessions over HTTP, posting test messages to `/run_sse`. - [logs-and-traces.md](references/logs-and-traces.md) — log levels and where each command writes them, the trace endpoints, span attributes, and the env vars that control whether prompts appear in spans. - [failure-modes.md](references/failure-modes.md) — ADK-specific symptoms with the cause and a concrete check for each. - [event-flow.md](references/event-flow.md) — how an invocation becomes events, callback order, the event fields that matter, and where each stage lives in the source. ## Ground rules - Leave sessions in place when you finish. The user may still want to open them in the web UI, and `adk web` has no undelete. - Delete any throwaway agent you created for a repro, unless the user asked to keep it. - Reach for a unit test in `tests/unittests/` when the bug is inside one component, and for a sample under `contributing/samples/` (see `adk-sample-creator`) when it only reproduces with runner, agent, and workflow wired together.

在 GitHub 查看

返回搜索返回安装

adk-setup

Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development checkout, install project dependencies, fix a missing or broken .venv, or prepare a machine for contributing a pull request. Don't use for debugging a running agent (use adk-debug), for commit and pull-request mechanics (use adk-git), or for re-running formatters on a checkout that is already set up (pre-commit run --all-files).

2026-10-12

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-10-12

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).

2026-10-09

查看这个仓库的全部 Skills

adk-debug

来源信息

安装方式

用 AI 助手安装

检查来源文件

同仓库更多 Skills

用 AI 助手安装

同仓库更多 Skills