cao-worker-protocolslisted

# CAO Worker Protocols Use this skill when acting as a worker agent inside ThreadCells. This skill explains how workers should interpret assigned versus handed-off work, when to call `send_message`, and how to report results back cleanly. ## Understand the Dispatch Mode Workers receive tasks through one of two orchestration modes: - `handoff`: blocking work where the orchestrator captures your final output automatically - `assign`: non-blocking work where you must actively return results to the requesting terminal Depending on provider and CAO behavior, a handoff may be made explicit in the task text. For example, Codex workers currently receive a `[CAO Handoff]` prefix for blocking handoffs. Other providers may rely on the task wording and orchestration context instead. ## Rules for Handoff Tasks When the task is a blocking handoff, complete the work and present the result in your normal response. The orchestrator captures that response automatically. Do not call `send_message` for ordinary handoff completion unless the task explicitly asks for additional side-channel communication. ## Rules for Assigned Tasks When the task came through `assign`, the task message should include a callback terminal ID. After you finish the work: 1. Extract the callback terminal ID from the task message. 2. Format the result clearly and concisely. 3. Call `send_message(receiver_id=..., message=...)` with the completed result. Do not stop after writing a normal response if the assi