Agent Communication Debugger

Diagnose A2A agent communication issues across WebSocket and RAG board transport layers.

Updated Sep 22, 2025

Search Tags:#routing #Python #orchestrator #log-analysis #A2A #agent-debugging

Ready to run

npx skills add https://github.com/EGAdams/planner --skill agent-communication-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Agent Communication Debugger
Source: https://github.com/EGAdams/planner/tree/main/.claude/skills/agent-debug
Command: npx skills add https://github.com/EGAdams/planner --skill agent-communication-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rich, a2a_communicating_agents, and includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and troubleshoot issues in the A2A (Agent-to-Agent) communication pipeline, including agent status checks, message routing, transport connectivity, and log analysis. Use it when messages are not delivered or agents are unresponsive, or when debugging orchestrator, coder-agent, or tester-agent communication problems.

Core Features & Use Cases

Systematic diagnostics: verify agent status, configurations, logs, and transport health.
Routing & delivery fixes: identify routing issues and fix topic mismatches.
Guided remediation: provides concrete steps to restart agents, validate API keys, and verify connectivity.
Use Case: If the orchestrator routes to the wrong agent, this Skill guides you through root-cause analysis and fixes.

Quick Start

Use the agent-debug skill to check current agent states, run a test message delivery, and follow the diagnostic workflow. Example: "Check agent status and test message delivery."

Frequently Asked Questions about Agent Communication Debugger

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

FAQPage Schema

How do I diagnose A2A agent communication failures?▼

A2A agent communication failures are diagnosed by checking agent status in agent.json, analyzing logs, verifying transport health across WebSocket and RAG board layers, and running test_message suites. This Skill automates that workflow for orchestrator, coder_agent, and tester_agent to identify routing misroutes, delivery failures, and configuration problems.

What causes message routing issues between agents?▼

Message routing issues occur when topic mismatches or orchestrator misconfiguration send messages to the wrong agent. This Skill identifies routing problems through log analysis and guided verification procedures, then provides concrete steps to fix topic routing and restart agents with corrected configurations.

How do I verify agent connectivity and transport health?▼

Verify agent connectivity by checking WebSocket and RAG board transport layer status, validating API keys, and running test message delivery suites. This Skill runs these diagnostics systematically across your agent network to confirm all communication paths are operational.

Can I debug unresponsive agents without restarting everything?▼

Yes. This Skill pinpoints which agent is unresponsive through status checks and log analysis, then guides targeted restart and reconnection procedures for only the affected agents, avoiding full system restarts.

What should I check first when agents stop communicating?▼

Start by checking current agent states and configurations, then run test message delivery to isolate whether the problem is agent status, routing logic, or transport connectivity. This Skill follows this diagnostic sequence to quickly identify root cause.

Does this work with custom orchestrator and agent setups?▼

Yes. This Skill applies to orchestrator, coder_agent, and tester_agent across their transport layers (WebSocket and RAG board), supporting both standard and custom A2A communication pipelines with agent.json configuration files.