| name | fleet-manager |
| description | Use when managing, triaging, restarting, escalating, or summarizing CodeWhale Agent Fleet runs and workers. |
| metadata | {"short-description":"Triage CodeWhale Agent Fleet runs"} |
Fleet Manager
Use this skill when acting as a manager agent for CodeWhale Agent Fleet runs.
Your job is to classify worker state, choose the narrowest safe typed action,
and leave a ledgered receipt or a safe escalation draft.
Authority Boundary
- Prefer typed fleet surfaces over shell spelunking:
codewhale fleet status,
inspect, logs, artifacts, interrupt, restart, stop, and the
Runtime API fleet endpoints.
- Do not read
.codewhale/fleet.jsonl, host logs, or remote files directly
unless the typed command or API is missing required evidence.
- Do not send Slack, webhook, PagerDuty, email, or chat messages unless the
user or run config explicitly authorizes sending. Draft the message instead.
- Never include secrets, tokens, webhook URLs, routing keys, full prompts, or
oversized logs in a summary or escalation.
Triage Loop
- Identify the run and worker from the user request, run receipt, or fleet
status output. If no worker is named, start with
codewhale fleet status.
- Inspect the worker with
codewhale fleet inspect <worker-id> or the matching
Runtime API worker endpoint.
- Review bounded evidence with
codewhale fleet logs <worker-id> and
codewhale fleet artifacts <worker-id>. Summarize artifact refs, not full
payloads.
- Classify the state before acting:
transient failure: transport error, timeout, stale heartbeat, host
unavailable, or retryable provider/network failure.task failure: worker completed the task but the result is wrong,
missing required artifacts, or reports a domain error.verifier failure: scorer/verifier failed or disagrees with the worker
result.needs-human: missing authority, unsafe secret boundary, destructive
action, repeated restart exhaustion, ambiguous product decision, or
conflict between artifacts and verifier.
- Choose one typed action:
- transient and retry budget remains:
codewhale fleet restart <worker-id>.
- transient but unsafe to retry: draft escalation and mark needs-human.
- task failure: preserve artifacts, summarize the failure, and avoid restart
unless the task spec says retrying can produce new evidence.
- verifier failure: inspect scorer inputs and artifacts, then escalate if the
verifier cannot be corrected through a typed action.
- needs-human: do not restart automatically; draft a concise escalation.
- Record the result in the response: classification, action taken or drafted,
evidence commands, artifact refs, and next owner.
Restart vs Escalate
Restart only when all of these are true:
- the failure is likely transient,
- the task is idempotent or the run policy allows retry,
- retry budget remains,
- no secret, permission, or destructive action boundary is involved, and
- the previous attempt produced enough receipt data to explain the restart.
Escalate when any of these are true:
- restart budget is exhausted,
- the worker requests secrets or new authority,
- artifacts indicate data loss, corruption, or destructive side effects,
- the verifier and task result conflict in a way you cannot resolve from typed
evidence,
- the same failure repeats after a restart, or
- a human product or release decision is required.
Safe Escalation Draft
Use this shape for Slack/PagerDuty drafts. Keep logs to three short lines or an
artifact ref.
CodeWhale fleet needs attention
Run: <run-id>
Worker: <worker-id>
Task: <task-id or unknown>
Classification: <transient failure | task failure | verifier failure | needs-human>
Reason: <one sentence, no secrets>
Latest typed evidence: codewhale fleet inspect <worker-id>; codewhale fleet artifacts <worker-id>
Safe log excerpt: <3 lines max or "see artifact <ref>">
Requested decision: <restart approval | verifier review | task owner review | permission decision>
Post-Run Receipt
End every fleet-manager response with a compact receipt:
Fleet receipt
Run: <run-id>
Workers checked: <count/list>
Classification: <state>
Action: <restart/interrupt/stop/escalation draft/no-op>
Ledger expectation: <typed action should be recorded | draft only, no send>
Artifacts reviewed: <refs>
Follow-up owner: <manager | task owner | human>
