worker

Coordinate OMX team tasks via ACK startup and mailbox-driven lifecycle in tmux.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill worker-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/worker
Command: npx skills add https://github.com/riethmayer/dotfiles --skill worker-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The worker protocol standardizes onboarding and ongoing task handling for OMX teams operating in tmux, reducing miscommunication and delays by enforcing an ACK-based startup and a disciplined mailbox-driven lifecycle.

Core Features & Use Cases

  • Startup protocol: ACK-based initialization and team-scoped identity management for new workers.
  • Inbox and mailbox workflows: read, claim, and process tasks from inbox to completion with structured statuses.
  • Task lifecycle management: coordinate task progression through claimed, in_progress, completed, or failed states with safe transitions and auditability.

Quick Start

Load the worker skill in your session and begin with an ACK initialization, followed by processing the mailbox tasks per the lifecycle.

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 states for a tmux-based team?

You coordinate tmux-based team task lifecycle states by enforcing an ACK startup protocol and using a mailbox-driven workflow to safely transition tasks through claimed, in_progress, completed, or failed statuses.

What is an ACK-driven task lifecycle and how does it work for team sessions?

An ACK-driven task lifecycle requires workers to send an ACK initialization signal to establish team-scoped identity, followed by reading inbox content and claiming tasks before progressing them through structured status transitions.

How do I claim and process tasks from a shared mailbox without conflicts?

Claim and process shared mailbox tasks safely by applying the canonical state resolution and claim-safe workflows specified in the worker protocol, ensuring no two workers process the same task simultaneously.

Does the worker protocol support CLI-driven task transitions for OMX teams?

Yes, the worker protocol supports CLI-driven task transitions for OMX teams, allowing workers to update task statuses and mailbox state directly through command-line interface commands for reliable collaboration.

Can I use this task lifecycle management approach without tmux?

No, this task lifecycle management approach is specifically designed for tmux-based team sessions where workers operate within a shared terminal multiplexer environment and rely on its session management capabilities.

What's the best way to onboard new workers into an OMX team session?

The best way to onboard new workers into an OMX team session is through the ACK-based initialization protocol, which establishes team-scoped identity and prepares them to read and process mailbox tasks.