a2a-patterns

Expose and consume AI agents via the A2A protocol across ADK deployments.

Updated Aug 23, 2026

Search Tags:#templates #multi-agent #adk #agent-to-agent #a2a-protocol #a2a-patterns

Ready to run

npx skills add https://github.com/RawleySM/rlm-adk --skill a2a-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a2a-patterns
Source: https://github.com/RawleySM/rlm-adk/tree/main/.gemini/skills/a2a-patterns
Command: npx skills add https://github.com/RawleySM/rlm-adk --skill a2a-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, uuidgen, gcloud, adk, kubectl, and includes scripts (resource) components.

What problem does it solve?

The A2A pattern suite enables agents to expose themselves and consume remote agents using the A2A protocol within Google's ADK, enabling secure multi-agent collaboration and orchestration.

Core Features & Use Cases

Exposing Agents via A2A (server-side) to make your ADK agent accessible to other agents, including an Agent Card at /.well-known/agent.json, a connected executor, and a lightweight HTTP/GRPC server.
Consuming External Agents (client-side) to integrate remote agents as sub-agents, with capability discovery, a send_task tool, and inter-agent session management.
Multi-Agent Orchestration to coordinate workloads across several specialist agents, with a coordinator that routes tasks, aggregates results, and supports example deployments.

Quick Start

Run the expose-agent script to deploy an A2A service or run the consume-agent script to connect to a remote A2A agent.

Frequently Asked Questions about a2a-patterns

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

FAQPage Schema

How do I expose an ADK agent to other agents using the A2A protocol?▼

To expose an ADK agent via A2A, you run a script that deploys a lightweight HTTP/GRPC server and generates an Agent Card at /.well-known/agent.json, enabling other agents to discover and communicate with your agent.

Can I connect a remote agent as a sub-agent in ADK?▼

Yes, you can consume external agents by running a script that integrates remote agents as sub-agents, providing capability discovery, a send_task tool, and managing inter-agent sessions for client-side consumption.

Does the A2A protocol support multi-agent orchestration across Cloud Run and GKE?▼

Yes, the A2A protocol supports multi-agent orchestration across ADK deployments including Cloud Run, Agent Engine, and GKE by using a coordinator that routes tasks, aggregates results, and manages workloads across specialist agents.

What dependencies do I need to deploy and test A2A integrations?▼

You need curl, jq, uuidgen, gcloud, adk, and kubectl installed to deploy, consume, and test A2A integrations, as these tools are required for running the validation steps and deployment scripts.

What is an Agent Card in the A2A protocol?▼

An Agent Card is a JSON file hosted at /.well-known/agent.json that allows an A2A server-side agent to expose its capabilities, enabling other agents to discover and interact with it within Google's ADK.

What's the best way to validate A2A agent communication before production?▼

The best way to validate A2A agent communication is by running the provided validation scripts to test server-side exposure and client consumption, ensuring your multi-agent orchestration works correctly before deploying to Cloud Run or GKE.