A2a agent delegation
Skill m00kk/agent-skills-playbook/skills/a2a-agent-delegation
15 production Agent Skills — MCP, LangGraph, RAG, security, Cursor SDK. MIT licensed.
npx -y skills add m00kk/agent-skills-playbook --skill a2a-agent-delegationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Designs agent-to-agent delegation using A2A-style handoffs: task envelopes, capability cards, and async responses. Use when multiple agents collaborate, Google A2A, cross-framework agents, or delegating subtasks between services.
SKILL.md
1.7 KB, as published. Nobody here has run it
A2A Agent Delegation
Concept
MCP connects one agent to tools. A2A connects agent to agent for delegated work.
Use both: MCP for databases/APIs; A2A (or your orchestrator) for specialist agents.
Delegation envelope
Each handoff should include:
{
"task_id": "uuid",
"goal": "Summarize Q3 earnings call transcript",
"constraints": ["max 500 words", "cite timestamps"],
"context_refs": ["doc://transcript-123"],
"reply_to": "orchestrator/session-id",
"deadline_sec": 300
}
Workflow
- [ ] Define agent capability card (what it accepts / rejects)
- [ ] Orchestrator validates task fits specialist
- [ ] Send envelope; receive task_id
- [ ] Poll or subscribe for completion (async)
- [ ] Merge result into orchestrator state; verify schema
Orchestrator rules
- Do not chain >3 hops without human visibility
- Idempotent task_ids for retries
- Propagate cancellation to child agents
- Log correlation IDs across agents
Failure modes
| Issue | Mitigation |
|---|---|
| Duplicate work | Idempotency keys |
| Stale context | Version context_refs |
| Runaway delegation | Max depth + budget cap |
Relation to LangGraph
- LangGraph supervisor node can call A2A client instead of inline subgraph
- Keep business logic in orchestrator graph; specialists stay replaceable
Pair with multi-agent-supervisor for in-process routing; A2A for cross-service.