worker

Automate OMX Team worker onboarding and task lifecycle management via tmux and omx CLI.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/eszxcvfd/ANIZAKI --skill worker-eszxcvfd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/eszxcvfd/ANIZAKI/tree/main/.agents/skills/worker
Command: npx skills add https://github.com/eszxcvfd/ANIZAKI --skill worker-eszxcvfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol standardizes the workflow for OMX Team workers operating inside tmux panes, enabling reliable startup, mailbox communication, and a structured task lifecycle.

Core Features & Use Cases

  • ACK-driven startup protocol: ensures workers announce readiness before processing tasks.
  • Inbox, mailbox, and task lifecycle: guides workers to read, claim, execute, and report on tasks safely.
  • CLI-based interoperability: uses omx team api commands to interact with the team lead and state.

Quick Start

Start a Codex session as an OMX Team worker and follow the ACK and mailbox workflow to claim 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 automate task lifecycle management for OMX Team workers in tmux?

Task lifecycle management for OMX Team workers is automated by applying an ACK-driven protocol that handles worker initialization, inbox processing, and leader-worker communication inside tmux panes. Workers safely claim, execute, and report on tasks using omx CLI commands.

How does the ACK-driven startup protocol work for tmux-based workers?

The ACK-driven startup protocol requires workers to announce readiness before processing tasks. During initialization, workers parse identity from the OMX_TEAM_WORKER environment variable, resolve the SKILL.md load path, and send an ACK signal to confirm they are ready to receive mailbox messages.

Can I use this protocol to manage mailbox messages and status updates without manual intervention?

Yes, you can use this protocol to manage mailbox messages and status updates without manual intervention. It guides workers to read, claim, execute, and report on tasks safely by prescribing automated task transitions via omx CLI interactions.

What is the best way to standardize leader-worker communication in OMX teams?

The best way to standardize leader-worker communication in OMX teams is to implement a structured mailbox workflow where workers apply an ACK-driven protocol. This ensures reliable startup, standardized task claiming, and safe status reporting via omx team api commands.

Do I need the omx CLI to handle task transitions in an OMX tmux team?

Yes, you need the omx CLI to handle safe task transitions in an OMX tmux team. The protocol prescribes interoperability exclusively through omx team api commands to interact with the team lead and manage the task lifecycle state.

Why does my OMX worker fail to process tasks after tmux initialization?

An OMX worker fails to process tasks after tmux initialization if the ACK-driven startup protocol is not completed. The worker must successfully parse identity from OMX_TEAM_WORKER, resolve the SKILL.md load path, and send an ACK before it can safely claim mailbox tasks.