← ClaudeAtlas

agent-communication-debuggerlisted

Diagnoses and debugs A2A agent communication issues including agent status, message routing, transport connectivity, and log analysis. Use when agents aren't responding, messages aren't being delivered, routing is incorrect, or when debugging orchestrator, coder-agent, tester-agent communication problems.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 82
Install: claude install-skill aiskillstore/marketplace
# Agent Communication Debugger Debug and diagnose issues with the A2A (Agent-to-Agent) communication system, including the orchestrator, coder-agent, tester-agent, and message transport layers. ## Prerequisites - A2A agent system located in `a2a_communicating_agents/` - Python 3.10+ environment - Access to agent logs in `logs/` directory - Agent configurations in respective `agent.json` files ## Instructions ### 1. Check Agent Status First, determine which agents are running: ```bash # Check all agent processes ps aux | grep -E "(orchestrator|coder|tester|websocket)_agent|main.py" | grep -v grep ``` Look for: - `orchestrator_agent/main.py` - `coder_agent/main.py` - `tester_agent/main.py` - `websocket_server.py` **Common issues:** - Agent process not found → Agent isn't running, needs to be started - Multiple instances → Duplicate processes causing conflicts ### 2. Inspect Agent Configurations Read the agent configuration files to verify capabilities and topics: ```bash # View orchestrator config cat a2a_communicating_agents/orchestrator_agent/agent.json # View coder agent config cat a2a_communicating_agents/coder_agent/agent.json # View tester agent config (if exists) cat a2a_communicating_agents/tester_agent/agent.json ``` **Verify:** - Agent names match expected values - Topics are correctly defined - Capabilities describe what the agent does - No JSON syntax errors ### 3. Check Agent Logs Examine logs for errors and message flow: ```bash # View orchestrat