worker

Manage OMX worker task lifecycle and mailbox acknowledgements in tmux sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives a Codex session a precise operating protocol for functioning as an OMX team worker, so it can acknowledge startup, read the right inbox, and execute assigned work without breaking task-state rules.

Core Features & Use Cases

  • Startup ACK: Sends a deterministic initialization acknowledgment to the lead before any work begins.
  • State-First Task Flow: Reads worker inboxes, claims tasks safely, completes or fails them through the proper lifecycle API, and updates worker status afterward.
  • Mailbox and Dispatch Handling: Checks team mailboxes, marks messages delivered, and follows leader instructions from the durable state system.
  • Shutdown Discipline: Handles shutdown requests with the required acknowledgments and exit sequence.
  • Use Case: A tmux-spawned worker receives an assignment, claims the task, performs the work, reports completion, and leaves the team state consistent.

Quick Start

Send the startup ACK, then read your inbox and follow the first unblocked task assigned to you.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I manage OMX worker task lifecycle and mailbox handling in tmux?

OMX worker task lifecycle management requires reading worker inboxes, claiming assigned tasks safely, processing dispatch messages, and reporting completion through team state without violating claim-safe state rules. This ensures deterministic CLI interop within tmux-spawned worker sessions.

What is the proper startup sequence for an OMX team worker?

The OMX team worker startup sequence requires sending a deterministic initialization acknowledgment to the lead before any work begins. After the startup ACK is sent, the worker reads its inbox and follows the first unblocked task assigned.

How does state-first task flow handle task claiming and completion?

State-first task flow reads worker inboxes, claims tasks safely, completes or fails them through the proper lifecycle API, and updates worker status afterward. This approach enforces claim-safe state rules to keep team state consistent throughout execution.

How do you handle shutdown requests for tmux-spawned worker sessions?

Shutdown requests for tmux-spawned worker sessions require specific acknowledgments and an exit sequence. The worker must handle the shutdown discipline by sending the required acknowledgments to maintain consistent team state before terminating.

Can I use a tmux-spawned worker to process dispatch messages from a durable state system?

Yes, tmux-spawned workers check team mailboxes, mark messages delivered, and follow leader instructions from the durable state system. This mailbox and dispatch handling ensures deterministic CLI interop and consistent task lifecycle execution.