worker

Coordinate tmux-based OMX team work with ACK, mailbox, and task lifecycle management.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/byonk19-svg/rt-scheduler --skill worker-byonk19-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/byonk19-svg/rt-scheduler/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/byonk19-svg/rt-scheduler --skill worker-byonk19-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a repeatable, auditable workflow for OMX team workers, ensuring consistent startup, inbox task handling, and shutdown procedures across tmux sessions.

Core Features & Use Cases

  • Startup ACK and identity discovery: worker announces readiness to the leader and initializes the correct team context.
  • Inbox-driven task lifecycle: read, claim, execute, and complete tasks with status updates and mailbox checks.
  • Dispatch discipline and shutdown: follows state-driven messaging and clean shutdown protocols to align team state.

Quick Start

Run a worker session (e.g., alpha/worker-2) and follow the startup ACK to join the team workflow.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I coordinate tmux-based team workflows for task lifecycle management?

You can coordinate tmux-based team workflows by standardizing ACK, mailbox, and task lifecycle management to ensure workers read inbox tasks, claim work, and report status to a leader. This protocol provides deterministic startup and state updates.

What is an OMX worker protocol for reliable tasking?

An OMX worker protocol is a standardized system for tmux sessions where workers announce readiness, check mailboxes, execute assigned tasks, and report completion status to a leader using structured messages and status files.

How do I start a tmux worker session to join a team workflow?

To start a tmux worker session, run a worker instance like alpha/worker-2 and follow the startup ACK sequence to announce readiness to the leader and initialize the correct team context for inbox task handling.

Does the OMX task lifecycle require a leader and worker hierarchy?

Yes, the OMX task lifecycle applies to team-based workflows where a leader manages dispatch and workers read inbox tasks, claim assignments, execute work, and report status updates through structured messages.

Can I use tmux for deterministic startup and clean shutdown in team protocols?

Yes, you can use tmux to enforce deterministic startup ACK sequences and state-driven clean shutdown protocols, ensuring team state alignment across all worker sessions.

Why does my worker session need inbox-driven task handling?

Inbox-driven task handling is needed to maintain a repeatable, auditable workflow where workers read, claim, execute, and complete tasks with status updates, ensuring consistent procedures across tmux sessions.