worker

Executes inbox-driven tasks with startup ACKs and lifecycle management for Codex-based teams.

1|Updated Mar 15, 2026

Search Tags:#workflow #tmux #inbox #lifecycle #task-management #worker #omx

Ready to run

npx skills add https://github.com/Linnanli/xClaw --skill worker-linnanli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/Linnanli/xClaw/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/Linnanli/xClaw --skill worker-linnanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Worker Skill enables Codex-based OMX team workers to participate in a tmux-driven workflow by handling startup acknowledgments, inboxed tasks, and a strict lifecycle for task completion. It provides a clear protocol for identifying team identity, loading tasks, claiming work, and transitioning task status under leader oversight.

Core Features & Use Cases

Startup ACK: Sends a deterministic acknowledgement to the team lead to join a new task lifecycle.
Inbox-driven Task Processing: Reads and executes tasks from the team inbox, ensuring claim-safe transitions.
Lifecycle Management: Enforces the in_progress to completed/failed transitions and clean worker state updates.

Quick Start

Initialize the worker by setting OMX_TEAM_WORKER, then send a startup ACK to the leader, and begin processing your inbox tasks.

Frequently Asked Questions about worker

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

FAQPage Schema

How do I manage OMX team tasks within a tmux session?▼

You can coordinate OMX team tasks by initializing a worker identity, sending a startup ACK to the team leader, and processing inbox-driven work with deterministic, claim-safe state transitions.

What is a startup ACK in task lifecycle management?▼

A startup ACK is a deterministic acknowledgement sent to the team leader to officially join a new task lifecycle, enabling the worker to begin claiming and processing inboxed tasks.

How does inbox-driven task processing handle claim-safe transitions?▼

Inbox-driven task processing enforces deterministic, claim-safe operations by loading tasks from the team inbox and applying explicit state updates to transition tasks to completed or failed.

Do I need to set OMX_TEAM_WORKER before processing inbox tasks?▼

Yes, you must set the OMX_TEAM_WORKER environment to initialize worker identity before sending a startup ACK to the leader and processing inboxed tasks.

Can I use this worker protocol for deterministic task claiming in Codex?▼

Yes, this protocol coordinates Codex-based OMX team workers by performing startup ACKs, claiming inboxed tasks deterministically, and enforcing lifecycle transitions with clean state updates.