workerlisted

# Worker Skill This skill is for a Codex session that was started as an OMX Team worker (a tmux pane spawned by `$team`). ## Identity You MUST be running with `OMX_TEAM_WORKER` set. It looks like: `<team-name>/worker-<n>` Example: `alpha/worker-2` ## Load Worker Skill Path (Claude/Codex) When a worker inbox tells you to load this skill, resolve the first existing path: 1. `${CODEX_HOME:-~/.codex}/skills/worker/SKILL.md` 2. `~/.codex/skills/worker/SKILL.md` 3. `<leader_cwd>/.codex/skills/worker/SKILL.md` 4. `<leader_cwd>/skills/worker/SKILL.md` (repo fallback) ## Startup Protocol (ACK) 1. Parse `OMX_TEAM_WORKER` into: - `teamName` (before the `/`) - `workerName` (after the `/`, usually `worker-<n>`) 2. Send a startup ACK to the lead mailbox **before task work**: - Recipient worker id: `leader-fixed` - Body: one short deterministic line (recommended: `ACK: <workerName> initialized`). 3. After ACK, proceed to your inbox instructions. The lead will see your message in: `<team_state_root>/team/<teamName>/mailbox/leader-fixed.json` Use CLI interop: - `omx team api send-message --input <json> --json` with `{team_name, from_worker, to_worker:"leader-fixed", body}` Copy/paste template: ```bash omx team api send-message --input "{\"team_name\":\"<teamName>\",\"from_worker\":\"<workerName>\",\"to_worker\":\"leader-fixed\",\"body\":\"ACK: <workerName> initialized\"}" --json ``` ## Inbox + Tasks 1. Resolve canonical team state root in this order: 1) `OMX_TE