worker

Name: worker
Availability: InStock
Author: gtpgg1013

Automate OMX worker task lifecycles with ACK, inbox, and mailbox status updates.

Updated Mar 21, 2026

Search Tags:#workflow #tmux #inbox #task-lifecycle #mailbox #ack #omx

Ready to run

npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill worker-gtpgg1013

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/gtpgg1013/claude-skills-collection/tree/main/skills/agents/worker
Command: npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill worker-gtpgg1013

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes OMX team worker protocols, ensuring reliable startup, inbox/task handling, and mailbox-based status updates.

Core Features & Use Cases

ACK-based startup and acknowledgment of tasks to establish clear ownership on each session.
Inbox-driven task lifecycles: claim, execute, and transition tasks to completed or failed with auditable state changes.
Mailbox-based communications: standardized messages and status reporting to keep the team state synchronized.

Quick Start

Load this skill in an OMX worker session and follow the inbox-driven task lifecycle from ACK to completion.

Frequently Asked Questions about worker

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

FAQPage Schema

How do I automate OMX team worker routines in tmux sessions?▼

Automate OMX team worker routines by loading this skill to enforce a consistent ACK, mailbox, and task lifecycle across tmux-based team sessions. It standardizes startup acknowledgment, inbox task reading, claiming, execution, and status reporting via prescribed file paths.

How does the ACK workflow coordinate task lifecycles for team workers?▼

The ACK workflow coordinates task lifecycles by requiring workers to acknowledge startup, claim inbox tasks, execute them, and transition states to completed or failed. This ensures orderly handoffs and auditable state changes synchronized through mailbox-based communications.

What is the best way to standardize task status reporting in a tmux worker session?▼

Standardize task status reporting by using mailbox-based communications to send prescribed messages and state updates. This keeps the OMX team state synchronized and ensures reliable handoffs during the inbox-driven task lifecycle.

Can I enforce orderly task handoffs and state transitions without external dependencies?▼

Yes, you can enforce orderly task handoffs and state transitions without external dependencies. This skill operates standalone, applying startup ACK, inbox task claims, and file-path-based status updates to manage the OMX worker lifecycle.

Why do my OMX team worker sessions lack consistent task ownership and state tracking?▼

OMX worker sessions lack consistency without a standardized protocol for task ownership and state tracking. This skill solves the problem by enforcing an ACK-based startup and a mailbox-driven lifecycle for auditable task transitions.