delegate

Route tasks to the best available agent or runtime with automatic adapter selection.

226|55|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Miosa-osa/canopy --skill delegate-miosa-osa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delegate
Source: https://github.com/Miosa-osa/canopy/tree/main/library/skills/coordination/delegate
Command: npx skills add https://github.com/Miosa-osa/canopy --skill delegate-miosa-osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates task routing to the most suitable workspace agent or runtime, improving speed, accuracy, and traceability of delegated work.

Core Features & Use Cases

  • Automatic adapter selection based on task characteristics to route to Claude, Codex, Gemini, or other adapters.
  • Parent chain tracking so every delegated task traces back to its origin for auditability.
  • Delegate to a specific agent or use auto-routing with options like --auto and --adapter to control target.
  • Dependency handling and result delivery to the caller, including sync-style waiting when required.
  • Use Case: delegating a complex reasoning task to Claude, bulk changes to Codex, or multimodal input to Gemini.

Quick Start

Delegate a task to the most suitable workspace agent using /delegate.

Frequently Asked Questions about delegate

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

FAQPage Schema
How do I route a task to the best available agent automatically?▼

You can route a task to the best available agent automatically by using the /delegate command with the --auto option. This enables automatic adapter selection based on task characteristics, ensuring efficient completion.

How does adapter selection work for multimodal inputs versus bulk changes?▼

Adapter selection works by matching task characteristics to specific runtimes: Claude for reasoning, Codex for bulk changes, and Gemini for multimodal inputs. You can also force a specific runtime using the --adapter option.

Can I trace a delegated task back to its original parent request?▼

Yes, you can trace a delegated task back to its origin because the system maintains a parent chain for delegation traceability. This ensures every routed task is auditable back to its initial caller.

What is the best way to handle dependencies when delegating tasks to agents?▼

The best way to handle dependencies when delegating tasks is to use the built-in dependency handling and result delivery features. The system manages task tracking and supports sync-style waiting to deliver results to the caller.

Does task routing support waiting for a delegated agent to finish before returning?▼

Yes, task routing supports sync-style waiting when required. It handles result delivery to the caller, ensuring the parent process can wait for the delegated agent to complete before continuing.

When should I manually specify an adapter instead of using auto-routing for task delegation?▼

You should manually specify an adapter using the --adapter option when you need strict control over the target runtime, overriding auto-routing to force a task to Claude, Codex, or Gemini based on specific requirements.