worker

Automate OMQ team worker onboarding and task lifecycle management in tmux.

2|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/chrisxue90/oh-my-qwencode --skill worker-chrisxue90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/chrisxue90/oh-my-qwencode/tree/main/skills/worker
Command: npx skills add https://github.com/chrisxue90/oh-my-qwencode --skill worker-chrisxue90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a protocol for OMQ teams to initialize workers, manage inboxes, and enforce a reliable task lifecycle during tmux sessions.

Core Features & Use Cases

  • Startup ACK protocol and identity parsing via OMQ_TEAM_WORKER.
  • Inbox, task claim, and status transitions to ensure deterministic collaboration.
  • Mailbox and dispatch discipline to maintain durable team state within .omq workspaces.

Quick Start

Load the worker skill in a tmux-based OMQ team session and follow the ACK startup, inbox tasks, and mailbox lifecycle.

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 a multi-person OMQ team in tmux?

To automate task lifecycle management for an OMQ team, this Skill enforces deterministic collaboration protocols within tmux sessions. It handles startup ACK, inbox task processing, and task claim transitions to maintain durable team state in .omq workspaces.

How does the startup ACK protocol work for tmux-based team worker onboarding?

The startup ACK protocol parses worker identity from the OMQ_TEAM_WORKER environment variable during tmux session initialization. It confirms worker readiness, establishes mailbox communications, and ensures every team member is registered before processing inbox tasks.

What is the best way to manage inbox tasks and claim work across multiple tmux workers?

The best way to manage inbox tasks across tmux workers is through the mailbox dispatch discipline this Skill provides. It defines explicit instructions for reading inboxes, claiming available tasks, and updating worker status to ensure deterministic, collision-free collaboration.

Do I need a specific environment setup to run OMQ team workflows in tmux?

Yes, you need a multi-person OMQ team operating within tmux and the OMQ_TEAM_WORKER variable configured for identity parsing. The Skill then uses the .omq workspace directory to maintain durable team state and mailbox communications.

Can I use this worker protocol to track task transitions and mailbox communications in .omq workspaces?

Yes, you can use this protocol to track task transitions and mailbox communications in .omq workspaces. It provides the necessary instructions for updating worker status and maintaining dispatch discipline to ensure durable team state during collaboration.

Why does my OMQ team need deterministic collaboration rules for tmux sessions?

Your OMQ team needs deterministic collaboration rules to prevent task claiming conflicts and ensure reliable task lifecycle management. This Skill enforces a startup ACK protocol and mailbox dispatch discipline to maintain consistent team worker state across tmux sessions.