dispatch

Route tasks to appropriate backends for execution with progress tracking.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/nq-rdl/agent-extensions --skill dispatch-nq-rdl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch
Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/dispatch
Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill dispatch-nq-rdl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route tasks to the appropriate backend for execution, enabling efficient use of external tools, parallelization, and specialized services.

Core Features & Use Cases

  • Backend selection: choose the most suitable backend based on task type, signal, or user instruction.
  • Four-step dispatch cycle: identify, choose, invoke, and track the dispatched task.
  • Backends and patterns: supports CLI tools, agent teams, and external services for scalable task execution.

Quick Start

Describe a task you want dispatched and I will route it to the best backend for execution.

Frequently Asked Questions about dispatch

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

FAQPage Schema
What is task routing and how does it help with backend orchestration?

Task routing sends work to the appropriate backend for execution, enabling parallelization and specialized service use. It applies a four-step dispatch cycle: identify, choose, invoke, and track the dispatched task across CLI tools, agent teams, or external services.

How do I automatically route tasks to specific backends like coding agents or search services?

Route tasks automatically by describing the task you want dispatched. The system identifies the task, selects the most suitable backend based on task type or user instruction, invokes it, and tracks progress with status reporting and error handling.

Can I use task dispatch patterns for large parallelizable work with external services?

Yes, task dispatch supports large, parallelizable, or tool-specific work that benefits from backends such as coding agents, search services, or team coordination. It defines dispatch patterns for CLI tools, agent teams, and external services for scalable task execution.

What's the best way to orchestrate agent teams and CLI tools for automated workflows?

Orchestrate agent teams and CLI tools using a dispatch cycle that identifies tasks, selects backends, invokes them, and tracks progress. This handles task routing via user instructions or issue metadata with integrated status reporting and error handling.

Does backend selection require specific dependencies to route tasks effectively?

No specific dependencies are required for backend selection. The system chooses the most suitable backend based on task type, signal, or user instruction, routing work to coding agents, search services, or team coordination without needing external setup.