adk-task-delegation

Delegate tasks between parent and sub-agents using the ADK 2.0 Task API.

2|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Folken2/nuvel --skill adk-task-delegation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adk-task-delegation
Source: https://github.com/Folken2/nuvel/tree/main/nuvel/backends/adk/skills/adk-task-delegation
Command: npx skills add https://github.com/Folken2/nuvel --skill adk-task-delegation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-adk, pydantic, and includes references (resource) components.

What problem does it solve?

This skill solves the complexity of managing multi-agent hierarchies by providing a standardized, type-safe way to delegate bounded work units between a parent agent and its sub-agents without manual plumbing.

Core Features & Use Cases

  • Task Delegation API: Automatically wires up delegation tools using ADK 2.0 modes (task, single_turn, chat) to keep execution within a single session.
  • Typed Contracts: Enforces input and output schemas using Pydantic models, ensuring sub-agents return validated data and parent agents pass structured requests.
  • Workflow Integration: Enables seamless migration from legacy agent wrappers to robust, graph-based workflows with explicit routing and error handling.

Quick Start

Configure an LlmAgent with mode set to task and define an output_schema to enable automatic finish_task tool attachment for validated sub-agent delegation.

Frequently Asked Questions about adk-task-delegation

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

FAQPage Schema
How do I delegate typed tasks between parent and sub-agents in ADK 2.0?

To delegate typed tasks in ADK 2.0, configure an LlmAgent with task mode and define an output_schema. This automatically attaches a finish_task tool, enabling structured data handoffs between parent and sub-agents.

How do I use Pydantic schemas for agent delegation inputs and outputs?

Pydantic schemas enforce typed contracts for agent delegation by validating input and output data. This ensures sub-agents receive structured requests and return validated data without requiring manual plumbing.

How do I migrate legacy agent wrappers to graph-based workflows?

Migrate legacy agent wrappers to graph-based workflows by implementing structured task delegation with the ADK 2.0 Task API. This approach provides explicit routing and robust error handling for multi-agent hierarchies.

Does ADK 2.0 support conditional routing for multi-agent orchestration?

ADK 2.0 supports conditional routing for multi-agent orchestration through its graph-based workflow structures. Typed data handoffs ensure bounded work units route correctly between parent and sub-agents.

What is the best way to keep sub-agent execution within a single session?

Keep sub-agent execution within a single session by using ADK 2.0 delegation modes like task, single_turn, and chat. The Task Delegation API automatically wires up these tools for robust multi-agent execution.

Why do I need typed contracts for multi-agent hierarchies?

Typed contracts are needed for multi-agent hierarchies to prevent manual plumbing and data mismatches. Enforcing Pydantic-validated input and output schemas ensures sub-agents process structured requests and return validated data.