skills.rest
wmasfoe
wmasfoeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

worker

Coordinate OMX team worker tasks and lifecycle across a tmux pane.

Updated Apr 23, 2026
Search Tags:#workflow#tmux#inbox#task-lifecycle#mailbox#ack#omx
One-click install
npx skills add https://github.com/wmasfoe/notch-pet --skill worker-wmasfoe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/wmasfoe/notch-pet/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/wmasfoe/notch-pet --skill worker-wmasfoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a consistent protocol for OMX team workers operating in a tmux pane, including identity validation, startup ACK, inbox/task lifecycle management, and safe mailbox coordination to keep teams synchronized.

Core Features & Use Cases

  • Identity enforcement: ensures workers run with OMX_TEAM_WORKER and exposes team/workers naming like <team-name>/worker-<n>.
  • ACK-based startup protocol: sends a startup ACK to the leader before processing tasks, enabling safe synchronization.
  • Inbox, tasks, and mailbox lifecycle: resolves state roots, reads inbox.md and task json files, claims tasks safely, and transitions tasks to completed/failed.
  • Dispatch discipline & shutdown: follows the state-first dispatch discipline and performs orderly shutdowns upon request.

Quick Start

Set OMX_TEAM_WORKER and follow the inbox/task lifecycle to claim, work on, and complete tasks.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I coordinate task lifecycle and worker synchronization across a tmux pane?▼

Task lifecycle coordination across a tmux pane relies on a startup ACK handshake to the leader, inbox processing for task claiming, and safe status transitions to keep workers synchronized.

What is the ACK handshake protocol for OMX team workers?▼

The ACK handshake protocol is a startup synchronization mechanism where an OMX team worker sends a startup ACK to the leader before processing tasks, ensuring safe team coordination within the tmux environment.

How do I set up OMX_TEAM_WORKER identity validation for task claiming?▼

OMX_TEAM_WORKER identity validation requires setting the OMX_TEAM_WORKER environment variable, which exposes team and worker naming like <team-name>/worker-<n> before loading skill paths and performing startup ACK.

How does inbox processing work for task state transitions in a workflow?▼

Inbox processing resolves state roots to read inbox.md and task json files, safely claims available tasks, and transitions task status to completed or failed based on execution results.

Can I use this worker protocol for orderly shutdowns and dispatch discipline?▼

Yes, the worker protocol follows a state-first dispatch discipline for processing tasks and performs orderly shutdowns upon request to maintain safe mailbox coordination across the OMX team.

Why do my OMX team worker tasks fail to synchronize in tmux?▼

Task synchronization failures in tmux often occur when the OMX_TEAM_WORKER identity is not parsed correctly or the startup ACK handshake to the leader is skipped before claiming inbox tasks.

Related Skills

Explore More Software Engineering Skills→
TienchingTienching
3

worker

Operate a tmux-based team worker with startup ACK and task lifecycle.

Community
Intermediate
hotaqhotaq

worker

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

Community
Advanced
andrew-t-jamesandrew-t-james

worker

Coordinate OMX team worker workflows in tmux sessions with startup ACK and task lifecycle management.

Community
Advanced
byonk19-svgbyonk19-svg

worker

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

Community
Intermediate