agent-dispatch

Translate orchestrator activation requests into subagent dispatch operations with result handling.

133|9|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill agent-dispatch-lync-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-dispatch
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/agent-dispatch
Command: npx skills add https://github.com/lync-cyber/CataForge --skill agent-dispatch-lync-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill translates orchestrator instructions into concrete subagent dispatch actions, so a workflow can activate the right agent, pass the right task context, and recover results consistently.

Core Features & Use Cases

  • Subagent Dispatch Translation: Converts high-level activation requests into runtime-specific dispatch operations.
  • Result Parsing & Recovery: Interprets structured agent outputs and falls back to filesystem-based recovery when responses are incomplete.
  • Safety & Scope Control: Enforces allowed-path validation to detect and roll back unauthorized writes.
  • Use Case: An orchestrator needs to launch a reviewer agent for a revision task, collect its structured result, and ensure any file changes stay within approved directories.

Quick Start

Use the agent-dispatch skill to route a task to the correct subagent, provide the task details and input documents, and return the result in the required structured format.

Frequently Asked Questions about agent-dispatch

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

FAQPage Schema
How do I dispatch subagents from an orchestrator agent safely?

Subagent dispatch translates high-level orchestrator activation requests into concrete runtime operations with structured prompt synthesis, passing task context and input documents to activate the correct agent consistently.

What is the best way to recover incomplete subagent responses during workflow orchestration?

Recovering incomplete subagent responses involves interpreting structured agent outputs and falling back to filesystem-based recovery, detecting incomplete data to ensure consistent result handling across phase-based workflows.

How does allowed-path validation prevent unauthorized writes in multi-agent execution?

Allowed-path validation enforces write-scope control during multi-agent execution by checking file changes against approved directories, detecting and rolling back any unauthorized writes attempted by dispatched subagents.

Can I use prompt templates for structured task handoff to a reviewer agent?

Structured prompt synthesis uses templates to route task details and input documents to the correct subagent, enabling consistent task handoff and returning results in the required structured format.

When do I need filesystem fallbacks for subagent result parsing?

Filesystem fallbacks are needed for subagent result parsing when structured agent outputs are incomplete, allowing the workflow to recover missing data and maintain consistent execution during phase-based orchestration.