worker

Coordinate OMX tmux worker roles via inbox task lifecycle and CLI status updates.

1|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/prthik/prathik-astro --skill worker-prthik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/prthik/prathik-astro/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/prthik/prathik-astro --skill worker-prthik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines a structured startup and task-workflow protocol for OMX tmux-based teams, enabling reliable coordination between workers and a lead through a formal ACK, inbox/task lifecycle, and status updates.

Core Features & Use Cases

  • Startup ACK: worker sends an acknowledgment to the lead mailbox before beginning work.
  • Inbox & Tasks: read unblocked tasks from the team inbox and claim them safely before execution.
  • Task Execution & Status: perform assigned work and transition tasks to completed or failed via the official CLI, updating your worker status accordingly.
  • Mailbox & Dispatch: interact with the mailbox and dispatch queues to maintain state consistency and predictable delivery.
  • Shutdown & Reentrancy: handle clean shutdown requests while preserving task integrity and recoverability.

Quick Start

Set OMX_TEAM_WORKER, read your inbox for an unblocked task, claim it safely, complete or fail it, and update your status via the team CLI as you work.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I coordinate tasks in a tmux-based team worker environment?

To coordinate tmux-based team worker roles, use a structured startup handshake and an inbox-driven task lifecycle. This protocol enforces reading inboxes, safely claiming tasks, and updating status via CLI to ensure deterministic, auditable execution.

How does an inbox-driven task lifecycle work for CLI workers?

An inbox-driven task lifecycle works by having workers read unblocked tasks from a team mailbox, claim them safely, and perform the work. Workers then transition tasks to completed or failed states by updating status through the official CLI.

Do I need to set environment variables before starting an OMX team worker?

Yes, you need to set the OMX_TEAM_WORKER environment variable. The protocol enforces specific environment checks before beginning work to ensure safe task execution and coordination with the team mailbox and dispatch system.

Why should I avoid directly modifying task state files in a team worker protocol?

You should avoid directly modifying task state files to ensure deterministic, auditable execution. The protocol requires using the official CLI to transition task lifecycle states safely, maintaining state consistency across the dispatch queues.

Can I handle clean shutdowns and task recovery with a tmux worker protocol?

Yes, the protocol supports clean shutdown requests while preserving task integrity and recoverability. It manages reentrancy by interacting with mailbox and dispatch queues to maintain predictable delivery and state consistency during shutdown.