dispatch-skills

Bind a selected work item to an execution carrier or specialized skill.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill dispatch-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch-skills
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/dispatch-skills
Command: npx skills add https://github.com/OceanEyeFF/servo --skill dispatch-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a single selected work item into a one-round, limited-scope dispatch decision, so the harness can execute that work through the most appropriate specialized skill or a safe fallback without expanding scope or inventing new skills.

Core Features & Use Cases

  • One-round limited-scope dispatching: Transitions the harness from WorktrackScope.dispatching by packaging the selected work item into a dispatch agreement and enforcing that it stays bounded to the single round.
  • Specialized skill matching with safe fallback: Chooses the semantically best dedicated skill when available (including document catch-up prioritization), otherwise routes execution through generic-worker-skill or a one-time task-specific instruction on the correct carrier.
  • Runtime dispatch mode governance: Applies override rules using .servo/control-state.md, respects runtime_dispatch_mode and policy-based selection in auto, and blocks behavior that would incorrectly claim delegation when delegating isn’t actually possible.

Quick Start

Ask the harness to dispatch the current worktrack action in WorktrackScope.dispatching using dispatch-skills so it selects the correct executor and returns a complete dispatch result.

Frequently Asked Questions about dispatch-skills

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

FAQPage Schema
How do I route a selected work item to the correct execution carrier in a dispatching workflow?

Agent routing for a selected work item is handled by binding it to the correct execution carrier or specialized skill for a single limited-scope round, ensuring safe and deterministic dispatch without expanding scope.

What happens during worktrack dispatching when no specialized skill matches my task?

Fallback handling routes the work item through generic-worker-skill or a one-time task-specific instruction on the correct carrier when a semantically best dedicated skill is unavailable, preventing the invention of new skills.

How does context budgeting enforce single-round limited-scope dispatch?

Context budgeting enforces single-round limited-scope dispatch by packaging the selected work item into a validated dispatch agreement, ensuring the harness stays bounded to that specific round and prevents end-to-end batch expansion.

Can I override automatic dispatch decision policy for agent routing?

Automatic dispatch decision policy can be overridden using .servo/control-state.md, which respects the runtime_dispatch_mode setting and applies policy-based selection rules during auto mode execution.

Why does my dispatch result incorrectly claim delegation when routing to an executor?

Incorrect delegation claims occur when execution carrier routing bypasses policy validation, which is why dispatch package validation and explicit delegation reporting are enforced to block false delegation claims.

Do I need an existing schedule package before starting worktrack dispatching?

Worktrack dispatching requires an existing schedule package that must be validated before use, as the process transitions the harness from WorktrackScope.dispatching without expanding into an end-to-end batch.