worker

Coordinate OMX team worker tasks across inboxes, mailboxes, and dispatch queues.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/pextacy/stellar --skill worker-pextacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/pextacy/stellar/tree/main/skills/worker
Command: npx skills add https://github.com/pextacy/stellar --skill worker-pextacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol enables reliable, synchronized teamwork for OMX teams operating in tmux by dictating startup, inbox-driven tasks, and lifecycle discipline.

Core Features & Use Cases

  • Startup ACK protocol to announce worker readiness and establish lead communication.
  • Inbox, mailbox, and task lifecycle management to claim, execute, and report task status.
  • Dispatch discipline and status updates to maintain consistent team state and allow smooth handoffs across team roles (worker, lead).

Quick Start

Start a Codex session as an OMX Team worker (teamName/worker-<n>) and follow the ACK and inbox-task lifecycle to begin work.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I coordinate OMX worker tasks end-to-end in tmux?

To coordinate OMX worker tasks end-to-end in tmux, use the startup ACK protocol to announce readiness, manage inbox-driven task claiming, execute work, and transition status for consistent team state. It handles dispatch discipline and state-first CLI interop.

What is the startup ACK protocol for team workflows?

The startup ACK protocol is a mechanism for OMX team workers to announce readiness and establish communication with the lead. It initiates the inbox-task lifecycle for claiming, executing, and reporting task status within synchronized team workflows.

How do I manage inbox and mailbox task claiming for team workers?

Manage inbox and mailbox task claiming by applying canonical inbox and task state handling. This ensures claim-safe transitions during task execution and status reporting, maintaining consistent team state for smooth handoffs across worker and lead roles.

Do I need tmux to run OMX worker task coordination?

Yes, tmux is required for OMX worker task coordination. The protocol is designed for OMX teams operating in tmux, using it to dictate startup, inbox-driven tasks, and lifecycle discipline for synchronized teamwork.

How does state-first CLI interop handle task lifecycle transitions?

State-first CLI interop handles task lifecycle transitions by enforcing canonical inbox and task state handling before executing CLI operations. This ensures claim-safe transitions and consistent dispatch discipline across worker and lead roles.