worker

Automate OMX Team worker protocol ACK, mailbox, and task lifecycle management.

Updated May 25, 2026
One-click install
npx skills add https://github.com/BetaS/swm-gis-workshop --skill worker-betas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/BetaS/swm-gis-workshop/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/BetaS/swm-gis-workshop --skill worker-betas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires omx-team-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the management of the OMX Team worker protocol, handling ACKs, mailbox interactions, and task lifecycle, streamlining the process for tmux-based OMX teams.

Core Features & Use Cases

  • ACK Management: Send and receive ACKs to and from the lead mailbox for initialization and status updates.
  • Inbox & Task Handling: Interact with the worker inbox and tasks, including claiming, executing, and completing tasks.
  • Mailbox Interactions: Check and process messages in the worker mailbox, following instructions from the lead.
  • Dispatch Discipline: Ensures that worker sessions treat team state and CLI interop as the source of truth.
  • Shutdown Protocol: Follows shutdown instructions exactly and exits the Codex session.
  • Use Case: Imagine you are part of an OMX team handling complex tasks. This Skill automates the workflow, allowing you to focus on the task at hand.

Quick Start

Load the worker skill and initialize by sending an ACK to the leader: omx team api send-message --input "{\"team_name\":\"<teamName>\",\"from_worker\":\"<workerName>\",\"to_worker\":\"leader-fixed\",\"body\":\"ACK: <workerName> initialized\"}" --json

Frequently Asked Questions about worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate task lifecycle management for tmux-based OMX teams?

Automating task lifecycle management for tmux-based OMX teams is handled by sending ACKs to the leader, claiming tasks from the worker inbox, executing them, and completing them. This Skill uses the OMX Team worker protocol and CLI interop for state synchronization across worker sessions.

How does ACK protocol initialization work for OMX team workers?

ACK protocol initialization for OMX team workers requires sending a message to the leader-fixed mailbox using the OMX API. The worker sends an ACK with its name to confirm initialization, which establishes communication and allows the worker to receive and process tasks.

What is the best way to manage worker mailbox interactions in a distributed task execution setup?

Managing worker mailbox interactions in distributed task execution involves checking the worker mailbox for instructions from the lead, processing messages, and treating team state and CLI interop as the source of truth. This dispatch discipline ensures workers follow the OMX Team protocol accurately.

Do I need the OMX API to run worker protocol automation in tmux?

Yes, you need the OMX API and CLI interop to run worker protocol automation in tmux. The system requires the omx-team-api dependency to send messages, handle ACKs, manage the mailbox, and synchronize task execution state across the team.

What happens during the shutdown protocol for an OMX team worker session?

During the shutdown protocol for an OMX team worker session, the worker follows shutdown instructions exactly as received from the lead and then exits the Codex session. This ensures clean termination and proper state synchronization across the tmux-based OMX team.