Individual skill
a2a-protocol
How agent-native apps discover, authenticate with, and call each other over A2A. Use when connecting one app to another, debugging a remote agent that won't authenticate, exposing skills to peers, or calling agents from scripts.
templates/dispatch/.agents/skills/a2a-protocol/SKILL.md
Source commit ff01b4009091c2140edb34d6f790ec64e7823356
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 7,645
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agents Repository topic
- ai Repository topic
- react Repository topic
- agent-native Repository topic
- typescript Repository topic
- agent-framework Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- framework Repository topic
- generative-ui Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# A2A Protocol (Agent-to-Agent)
## Rule
Agents call other agents over A2A, a JSON-RPC protocol for discovery and
delegation. Use it only when the user explicitly asks to involve a peer, or
the requested outcome requires data, credentials, or a capability owned by
that peer and unavailable through the local app's actions. The local app's
actions are the default; a peer's availability or ability to enrich a result
is not enough. When a peer supplies input, keep authoring and editing artifacts
native to the local app here.
When a handoff qualifies under the rule above, preserve the peer boundary: do
not have app A generate and execute raw SQL against app B's database, or expose