worker

Coordinate OMX team workers through ACK startup and inbox-driven task lifecycles.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill worker-ozby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/ozby/node-pubsub --skill worker-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates coordination of OMX team workers from startup to task completion.

Core Features & Use Cases

  • ACK-driven startup flow: workers announce readiness to the lead and await instructions.
  • Inbox-driven task lifecycle: read, claim, execute, and complete or fail tasks with proper transitions.
  • Mailbox & dispatch integration: coordinates with leader mailbox and dispatch state to keep team state consistent.

Quick Start

Run this skill in a Codex session as an OMX team worker, then read your inbox, claim tasks safely, perform work, and transition tasks to completed or failed using the prescribed CLI templates.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I coordinate OMX team workers from startup to task completion?

Task lifecycle coordination for OMX team workers is automated by enforcing a startup ACK protocol, reading inbox instructions, claiming tasks, and updating persistent status through a leader mailbox to keep team state consistent.

What is the ACK protocol for team workflow startup in Codex sessions?

The ACK protocol for team workflow startup requires workers to announce their readiness to the lead and await instructions before reading their inbox, ensuring orderly task sequencing and safe claim transitions within the dispatch state.

How do I safely claim and release tasks in an inbox-driven team workflow?

Inbox-driven task workflows allow workers to safely claim and release tasks by applying prescribed CLI templates that transition tasks through read, claim, execute, and complete or fail states while coordinating with the leader mailbox.

Can I use mailbox and dispatch integration to keep team state consistent?

Mailbox and dispatch integration coordinates with the leader mailbox and dispatch state to persistently update the team state root, ensuring team state consistency across all workers during task execution and lifecycle transitions.

Does worker task management require specific dependencies or components?

Worker task management requires no external dependencies or components, operating entirely within Codex sessions using inbox-driven task sequencing and persistent status updates to the team state root.

Why are my team worker task transitions failing during the OMX lifecycle?

Task lifecycle transitions fail when workers bypass the startup ACK protocol or skip prescribed CLI templates for claim, release, and status updates, causing inconsistent dispatch state and mailbox synchronization errors.