adk-debug

Diagnose Google ADK agent, tool, and session state issues in MemRAG.

18|6|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill adk-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adk-debug
Source: https://github.com/minh2004pd/chatbotfullpipeline/tree/main/.claude/skills/adk-debug
Command: npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill adk-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to diagnosing and fixing issues within Google ADK agents, their tools, session state handling, and multi-agent communication in MemRAG.

Core Features & Use Cases

  • Structured diagnostic workflow guiding checks on tool signatures, agent tooling, and system prompts
  • Step-by-step remediation playbook for common ADK issues like tool invocation failures, misrouted requests, or lost session state
  • Use Case: When an ADK-based MemRAG project experiences tool not called, sub-agent misinterpretation, or inconsistent user context, this Skill yields a clear diagnostic path and fixes

Quick Start

Follow the diagnostic workflow to identify the ADK agent issue and apply the recommended fixes.

Frequently Asked Questions about adk-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug ADK agent tool invocation failures in MemRAG?

To debug ADK agent tool invocation failures in MemRAG, follow a structured diagnostic workflow that enforces strict checks on tool signatures and agent tool registrations to identify and fix mismatches.

Why does my Google ADK multi-agent system misroute requests to the wrong sub-agent?

Google ADK multi-agent systems misroute requests due to misconfigured prompts. Diagnosing this involves checking agent tool registrations and system prompts to guide step-by-step remediation for correct routing.

How do I fix inconsistent session state across multi-agent communication in ADK?

Fixing inconsistent session state across ADK multi-agent communication requires enforcing strict checks on session propagation and logging configurations to identify missing context and apply remediation steps.

What is the best way to diagnose rate-limit errors in ADK agents?

The best way to diagnose ADK agent rate-limit errors is to apply a structured diagnostic workflow that checks logging configurations and agent tool registrations, guiding targeted remediation steps.

Can I use this diagnostic workflow for missing session state in non-MemRAG ADK projects?

This diagnostic workflow specifically targets missing session state and multi-agent communication issues within MemRAG ADK projects, enforcing strict checks on session propagation to yield a clear diagnostic path.