worker

Coordinate OMX worker task lifecycles via inbox and ACK protocols.

24|2|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill worker-orinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill worker-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supervisors and teams using OMX often face miscommunication and drift when coordinating worker initialization, inbox task reception, and status reporting. The Worker Skill defines a standardized ACK/init handshake and a deterministic task lifecycle to ensure everyone follows a single, auditable process.

Core Features & Use Cases

  • ACK-based startup: worker announces readiness to the lead, ensuring alignment before work begins.
  • Inbox-driven lifecycle: read, claim, execute, and report task progress in a repeatable flow.
  • CLI and mailbox templates: provides clear interop guidance for omx team api commands and status updates.
  • Stateful coordination: preserves consistent team state for traceability and recovery.

Quick Start

Initialize a worker session, announce readiness to the lead mailbox, and await the next inbox task.

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 worker tasks and report status to a lead mailbox?

You can coordinate tmux-based worker tasks using an OMX worker protocol that implements an ACK-based startup handshake and an inbox-driven lifecycle to claim, execute, and report task status to a lead mailbox.

What is the OMX worker protocol for task lifecycle management?

The OMX worker protocol is a deterministic task lifecycle process where workers announce readiness via an ACK handshake, receive inboxed tasks, execute them, and report status updates to a lead mailbox for stateful coordination.

How do I start a worker session and announce readiness to the lead mailbox?

To start a worker session, initialize the tmux-based OMX environment, send a startup ACK protocol message to the lead mailbox to announce readiness, and await the next inboxed task assignment.

Can I use the OMX team api for CLI interop in tmux team sessions?

Yes, the OMX worker protocol provides CLI interop guidance for omx team api commands, defining specific message formats and mailbox templates to ensure deterministic communication across tmux team sessions.

Why does my OMX team workflow suffer from miscommunication and state drift?

OMX team workflows suffer from miscommunication without a standardized ACK/init handshake and deterministic task lifecycle, which ensures consistent team state preservation for traceability and recovery.

Does the worker protocol require a specific environment to execute inbox tasks?

The worker protocol requires a tmux-based OMX team session environment to execute inbox tasks, utilizing mailbox templates and the omx team api for stateful coordination and status reporting.