Awesome-omni-skill a2a-sdk

Comprehensive Agent2Agent (A2A) JavaScript SDK skill for building A2A-compliant agents and clients. Use when implementing or integrating @a2a-js/sdk, creating A2A servers/clients, using JSON-RPC/REST/gRPC transports, streaming task updates, handling tasks/artifacts, authentication, or push notifications.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/backend/a2a-sdk" ~/.claude/skills/diegosouzapw-awesome-omni-skill-a2a-sdk && rm -rf "$T"

manifest: skills/backend/a2a-sdk/SKILL.md

source content

A2A JavaScript SDK Skill

Overview

Use this skill to implement A2A-compliant servers and clients with @a2a-js/sdk, including tasks, streaming, authentication, and transport selection. Follow A2A protocol v0.3.0.

Core Workflows

Select transport: JSON-RPC (default), REST, or gRPC.
Define an AgentCard and AgentExecutor for server implementations.
Use ClientFactory for client creation and message exchange.
Add task handling and artifacts for long-running operations.
Use streaming when real-time updates are required.
Add authentication or push notifications when needed.

Bundled Resources

```
README.md
```
: Quick overview and basic usage patterns.
```
REFERENCE.md
```
: Full API reference and advanced features.
```
HELPERS.md
```
: Helper utilities and common patterns.
```
templates/server/basic-server.ts
```
: Minimal server template.
```
templates/server/task-server.ts
```
: Task-based server template.
```
templates/client/basic-client.ts
```
: Minimal client template.
```
templates/client/streaming-client.ts
```
: Streaming client template.
```
examples/authentication.md
```
: Authentication server/client examples.
```
examples/streaming.md
```
: Streaming server/client examples.

Implementation Guidance

Keep AgentCard fields aligned with protocol v0.3.0.
Prefer direct message responses for simple requests.
Use tasks for long-running work and publish status updates and artifacts.
Use streaming for real-time task progress updates.
Include authentication via custom user builders or authenticated transports when required.