worker

Coordinates OMX team worker sessions through mailbox messaging and claim-safe task lifecycle.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill worker-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/worker
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill worker-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Codex session is spawned as a worker in a tmux-based OMX team, it needs a deterministic protocol to announce itself, receive tasks, claim work safely, and report completion without corrupting shared team state. This Skill defines that exact protocol so distributed workers coordinate reliably through files and CLI interop instead of ad-hoc tmux keystrokes. ## Core Features & Use Cases - Startup ACK Protocol: Parses the OMX_TEAM_WORKER identity and sends a deterministic acknowledgment to the leader mailbox before any task work begins. - Claim-Safe Task Lifecycle: Reads inbox assignments, claims tasks via omx team api claim-task, and transitions status to completed or failed without directly editing lifecycle fields. - Mailbox and Dispatch Discipline: Treats team state files and omx team api commands as the source of truth, with copy-paste CLI templates for listing and acknowledging messages. - Use Case: A leader spawns three workers to refactor separate modules; each worker loads this Skill, ACKs startup, claims its assigned task JSON, completes the work, and reports status back through the shared team state root. ## Quick Start Load the worker skill, send your startup ACK to the leader mailbox, then read your inbox and claim your first unblocked task using the omx team api commands.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I acknowledge startup as an OMX team worker?

Parse the OMX_TEAM_WORKER variable into team name and worker name, then send a one-line ACK to the leader-fixed mailbox using omx team api send-message before starting any task work.

How do I claim and complete a task in an OMX team?

Read your inbox, pick the first unblocked task, claim it with omx team api claim-task, do the work, then transition status from in_progress to completed or failed via omx team api transition-task-status. Never edit lifecycle fields directly in task files.

What task id format does the OMX state API use?

The MCP/state API uses the numeric id such as "1", not the prefixed form "task-1". Task files are named task-<id>.json under the team state root, but API calls reference only the numeric identifier.

Can workers rely on tmux send-keys for task dispatch?

No. Workers should treat team state files and omx team api commands as the source of truth. A tmux send-keys nudge is only a prompt to re-check inbox and mailbox state, never a primary delivery channel.

When should a worker use the Team Big Five coordination checklist?

Use it when tasks involve dependencies, shared files, handoffs, integration points, or changed assumptions. Isolated tasks with no shared surfaces only need the standard ACK, claim, verification, and completion flow.