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,778
フォーク: 4,129

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

AI アシスタントでインストール

このプロンプトをコピーして、使用中の 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

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？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-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

adk-review

Reviews the uncommitted changes in an adk-python working tree and reports correctness, design, public-API stability, test, sample and documentation gaps as a prioritized findings report, fixing them only when asked. Use when the user asks to review local changes, wants a self-review before opening a pull request, asks whether a change breaks the public API or needs tests, samples or docs, or asks what is wrong with the current diff. Required for changes to public APIs, core architecture (Runner, Workflow, BaseNode), new features and major refactors. Don't use for a single style nit (use adk-style), for diagnosing a failing test or a misbehaving agent at runtime (use adk-debug), or for wording a commit message or PR description (use adk-git).

2026-10-09

adk-style

Python style and codebase conventions for ADK (Agent Development Kit): private-by-default file visibility, imports, type hints, Pydantic v2 models, formatting, docstrings, logging, async I/O, file and test layout, and unit test structure. Use when writing or editing ADK source or tests, deciding whether a new file or symbol should be public or private, naming or placing a test file, fixing a formatter, linter, or type-check failure (pyink, isort, ruff, mypy, addlicense, compliance-checks), or asking whether code matches house style. Don't use for reviewing a whole changeset (use adk-review), writing a developer guide or design doc for a code unit (use adk-unit-guide or adk-unit-design), building or configuring agents (use adk-agent-builder), or installing the toolchain (use adk-setup).

2026-10-08

このリポジトリのすべてを見る

adk-debug

ソース情報

インストール方法

AI アシスタントでインストール

ソースファイルを確認

このリポジトリの他の Skills

AI アシスタントでインストール

このリポジトリの他の Skills