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월 20일 23:46
감지된 SKILL.md 언어: 영어
스타: 22,005
포크: 4,246

설치 방법

기본적으로 소스를 먼저 확인하는 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

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? 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-22

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

이 저장소의 모든 Skills 보기

adk-debug

소스 정보

설치 방법

AI 어시스턴트로 설치

소스 파일 검토

이 저장소의 다른 Skills

AI 어시스턴트로 설치

이 저장소의 다른 Skills