Fleet Dispatch (pack peer surface)
You receive an "invoke skill fleet-dispatch" command from a pack peer (the operator's control host). The command payload is a free-text string with both the role and the spec, like:
invoke skill fleet-dispatch --role agent --spec <spec text>
Your job is to invoke YOUR local fleet ladder to dispatch that spec on the named rung, and return the answer.
The public pack ships no resolver and no Fleet executable. This skill assumes the deployment provides scripts/fleet.py and config/fleet_ladder.yaml (see fleet-ladder). If either is missing, stop and return {"ok": False, "error": "fleet_resolver_missing"} — never improvise a resolver.
Steps
Parse the command for the role and the spec. The format is:
invoke skill fleet-dispatch --role <role> --spec <spec>
where <role> is one of agent, bot, builder, grader, worker, ... (see your local config/fleet_ladder.yaml), and <spec> is the free-text work to hand the model.
Invoke your local fleet resolver:
python3 scripts/fleet.py build --role <role> --spec <spec>
The fleet resolver:
- reads
config/fleet_ladder.yaml for the live rung order
- probes each provider's availability (live, never from memory)
- dispatches to the first AVAILABLE rung
- prints the model's answer, then a
FLEET_RECEIPT <json> line on stdout
Parse the response:
- Answer: everything on stdout that is NOT
FLEET_STATUS*, FLEET_RECEIPT*, or fleet:* lines. Strip those prefixes; the remaining lines are the model's answer.
- Receipt: the JSON after
FLEET_RECEIPT on its own line. Carries model, provider, route_chosen, latency_ms, cost_estimate, dispatch.
Return BOTH to the caller (the control host, over its own transport). The caller wraps the receipt in its signed execution receipt, so the full provenance chain is preserved end to end.
What you never do
- Never hand-build a model call. Never hardcode a model name. Never invent a provider.
- Never skip the fleet resolver and call a provider directly. The resolver owns the rung order and the harness fallback; bypassing it is a defect.
- Never silence a FLEET_RECEIPT. The receipt is the provenance record (
invariant-floor law 9).
- Never fall back silently on a missing credential (
invariant-floor laws 5 and 6: loud failures, no hidden gates; the ladder fails loud).
Failure handling
- If
python3 scripts/fleet.py build exits non-zero, return the stderr verbatim + the FLEET_RECEIPT if present.
- If the answer is empty, return
{"ok": False, "error": "fleet_empty_answer"} and the receipt (so the caller knows which rung was attempted).
- Never retry the same provider on the same error in a tight loop. The fleet resolver already retries with bounded backoff. If it gives up, you give up (
invariant-floor law 19 and bounded-loops: no hammering).
1---2name: fleet-dispatch3description: "Use when this agent receives an \"invoke skill fleet-dispatch\" command from a pack peer (another agent on the operator's control host), or when this agent needs to dispatch its own fleet rung for its own work. Calls scripts/fleet.py build --role <role> --spec <spec> against the local fleet ladder, parses FLEET_RECEIPT, returns the answer with provenance. Model-agnostic — the fleet_ladder.yaml owns the rung order, the agent just asks. Trigger words: fleet-dispatch, fleet rung, dispatch, role agent, role bot, invoke skill, fleet ladder."4license: MIT5metadata:6 source: https://skillmd.com/skills/tcuzzo/fleet-dispatch7---89# Fleet Dispatch (pack peer surface)1011You receive an "invoke skill fleet-dispatch" command from a pack peer (the operator's control host). The command payload is a free-text string with both the role and the spec, like:1213```14invoke skill fleet-dispatch --role agent --spec <spec text>15```1617Your job is to invoke YOUR local fleet ladder to dispatch that spec on the named rung, and return the answer.1819The public pack ships no resolver and no Fleet executable. This skill assumes the deployment provides `scripts/fleet.py` and `config/fleet_ladder.yaml` (see `fleet-ladder`). If either is missing, stop and return `{"ok": False, "error": "fleet_resolver_missing"}` — never improvise a resolver.2021## Steps22231. Parse the command for the role and the spec. The format is:24 `invoke skill fleet-dispatch --role <role> --spec <spec>`25 where `<role>` is one of `agent`, `bot`, `builder`, `grader`, `worker`, ... (see your local `config/fleet_ladder.yaml`), and `<spec>` is the free-text work to hand the model.26272. Invoke your local fleet resolver:28 ```bash29 python3 scripts/fleet.py build --role <role> --spec <spec>30 ```31 The fleet resolver:32 - reads `config/fleet_ladder.yaml` for the live rung order33 - probes each provider's availability (live, never from memory)34 - dispatches to the first AVAILABLE rung35 - prints the model's answer, then a `FLEET_RECEIPT <json>` line on stdout36373. Parse the response:38 - **Answer**: everything on stdout that is NOT `FLEET_STATUS*`, `FLEET_RECEIPT*`, or `fleet:*` lines. Strip those prefixes; the remaining lines are the model's answer.39 - **Receipt**: the JSON after `FLEET_RECEIPT ` on its own line. Carries `model`, `provider`, `route_chosen`, `latency_ms`, `cost_estimate`, `dispatch`.40414. Return BOTH to the caller (the control host, over its own transport). The caller wraps the receipt in its signed execution receipt, so the full provenance chain is preserved end to end.4243## What you never do4445- Never hand-build a model call. Never hardcode a model name. Never invent a provider.46- Never skip the fleet resolver and call a provider directly. The resolver owns the rung order and the harness fallback; bypassing it is a defect.47- Never silence a FLEET_RECEIPT. The receipt is the provenance record (`invariant-floor` law 9).48- Never fall back silently on a missing credential (`invariant-floor` laws 5 and 6: loud failures, no hidden gates; the ladder fails loud).4950## Failure handling5152- If `python3 scripts/fleet.py build` exits non-zero, return the stderr verbatim + the FLEET_RECEIPT if present.53- If the answer is empty, return `{"ok": False, "error": "fleet_empty_answer"}` and the receipt (so the caller knows which rung was attempted).54- Never retry the same provider on the same error in a tight loop. The fleet resolver already retries with bounded backoff. If it gives up, you give up (`invariant-floor` law 19 and `bounded-loops`: no hammering).