worker

Manage OMX team worker identity, inbox tasks, and mailbox communications.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill worker-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/YeaChan05/Remittance --skill worker-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized worker protocol for OMX teams, enabling reliable startup, identity handling, and task lifecycle management through ACKs, inbox processing, and mailbox communications.

Core Features & Use Cases

  • Startup protocol and identity parsing: Validates OMX_TEAM_WORKER environment and team/worker naming, performs an initial ACK to the leader before any work.
  • Inbox-driven task lifecycle: Reads inbox, claims tasks safely, processes tasks, and transitions status using provided CLI tooling.
  • Mailbox and dispatch coordination: Interacts with mailbox and dispatch state to ensure ordered delivery and state-first governance, with support for task claiming, release, and requeue as needed.
  • Shutdown and reliability: Respects shutdown instructions and updates worker status accordingly.

Quick Start

Start by running the worker with a valid OMX_TEAM_WORKER, then read and claim tasks from your inbox to drive the lifecycle from in_progress to completed.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I manage task lifecycle and ACKs for distributed tmux workers?

Manage distributed tmux worker task lifecycles by validating worker identity through OMX_TEAM_WORKER, sending an initial ACK to the leader, and using CLI tooling to claim inbox tasks and transition statuses safely.

What is the OMX team worker protocol for inbox-driven task processing?

The OMX team worker protocol is a standardized system for reading inbox tasks, claiming them safely, processing the work, and transitioning task status from in_progress to completed using provided CLI tools.

How do I set up a worker in an OMX team workflow environment?

Set up an OMX team worker by configuring the OMX_TEAM_WORKER environment variable, validating team and worker naming conventions, and performing an initial ACK to the leader before processing any inbox tasks.

Can I requeue or release tasks when coordinating mailbox communications across multiple workers?

Yes, you can requeue or release tasks during mailbox and dispatch coordination to ensure ordered delivery and state-first governance across multiple distributed workers.

Do I need specific environment variables to perform task claiming and status transitions?

Yes, you need the OMX_TEAM_WORKER environment variable set along with standardized inbox and state files to perform task claiming, status transitions, and acknowledgment operations.

What happens when a distributed worker receives shutdown instructions?

When a distributed worker receives shutdown instructions, the protocol respects the command and updates the worker status accordingly to ensure reliable team workload termination.