What problem does it solve? When a Codex session is spawned as a worker in a tmux-based OMX team, it needs a deterministic protocol to announce itself, receive tasks, claim work safely, and report completion without corrupting shared team state. This Skill defines that exact protocol so distributed workers coordinate reliably through files and CLI interop instead of ad-hoc tmux keystrokes. ## Core Features & Use Cases - Startup ACK Protocol: Parses the OMX_TEAM_WORKER identity and sends a deterministic acknowledgment to the leader mailbox before any task work begins. - Claim-Safe Task Lifecycle: Reads inbox assignments, claims tasks via omx team api claim-task, and transitions status to completed or failed without directly editing lifecycle fields. - Mailbox and Dispatch Discipline: Treats team state files and omx team api commands as the source of truth, with copy-paste CLI templates for listing and acknowledging messages. - Use Case: A leader spawns three workers to refactor separate modules; each worker loads this Skill, ACKs startup, claims its assigned task JSON, completes the work, and reports status back through the shared team state root. ## Quick Start Load the worker skill, send your startup ACK to the leader mailbox, then read your inbox and claim your first unblocked task using the omx team api commands.