worker

Operate a tmux-based team worker with startup ACK and task lifecycle.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol standardizes the operation of a tmux-based CodeBuddy team worker, ensuring a reliable startup handshake, mailbox-driven task flow, and deterministic task lifecycle.

Core Features & Use Cases

  • Identity & startup: parse OMB_TEAM_WORKER and send a startup ACK before starting work.
  • Inbox-driven workflow: read and claim tasks from the team inbox, then progress through in_progress to completed/failed.
  • Mailbox discipline: interact with the team mailbox for dispatch and status updates, enabling predictable collaboration.
  • Shutdown & recovery: respond to shutdown signals and resume or idle cleanly.

Quick Start

Load the worker skill in your CodeBuddy session and follow the ACK-initialization sequence to begin processing tasks.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I manage a tmux-based team worker for task processing?

To manage a tmux-based team worker, load the worker skill to enforce a startup ACK handshake, parse the OMB_TEAM_WORKER environment variable, and process tasks from the team inbox through a structured claim and transition lifecycle.

What is the task lifecycle for a team worker using a tmux inbox?

The task lifecycle for a tmux inbox worker involves reading tasks from the mailbox, claiming them, and progressing their status from in_progress to completed or failed. This ensures deterministic task tracking and predictable team collaboration.

How do I start a CodeBuddy team worker session correctly?

To start a CodeBuddy team worker session, load the worker skill and follow the ACK-initialization sequence to send a startup acknowledgment before reading the team mailbox and beginning task processing.

Do I need any specific environment variables to operate a team worker?

Yes, operating a team worker requires the OMB_TEAM_WORKER environment variable to establish worker identity. The skill relies on this variable alongside leader messaging and CLI interop to read inboxes and update task statuses.

Can I recover or shut down a tmux team worker cleanly during a task?

Yes, the worker skill includes shutdown and recovery mechanisms that respond to shutdown signals and allow the tmux worker to resume or idle cleanly without disrupting the current inbox task lifecycle.

Why does my team worker fail to claim tasks from the mailbox?

A team worker fails to claim tasks if the startup ACK handshake is not completed or the OMB_TEAM_WORKER environment variable is missing. Proper CLI interop and mailbox discipline are required to successfully read and claim inbox tasks.