team

Orchestrate coordinated agents on shared task lists via tmux-based execution.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill team-ozby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/team
Command: npx skills add https://github.com/ozby/node-pubsub --skill team-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple agents on a shared task list can be fragile without durable, observable orchestration. The Team Skill provides a tmux-based execution model for OMX that coordinates Codex and Claude workers, enforces lifecycle guarantees, and surfaces startup and progress evidence via a unified runtime.

Core Features & Use Cases

  • Durable multi-agent coordination across long-running tasks using tmux panes and a shared state store.
  • API-driven mutations and status visibility via the OMX toolset to manage task lifecycles, worker inboxes, and progress.
  • Use cases include parallel data processing, evaluation tasks, or multi-step workflows that require auditable startup/shutdown evidence and reliable progress tracking.

Quick Start

Launch a coordinated team session by running omx team <N:agent-type> "<task description>" and monitor progress with omx team status until completion.

Frequently Asked Questions about team

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

FAQPage Schema
How do I coordinate multiple agents on a shared task list?

Multi-agent coordination on a shared task list is handled through tmux-based orchestration, which manages parallel workstreams and enforces lifecycle guarantees across Codex and Claude workers using a shared state store.

How do I monitor progress across parallel multi-agent workflows?

You can monitor multi-agent workflow progress using the `omx team status` command, which surfaces runtime-state evidence and reliable progress tracking for all coordinated team members.

Does tmux-based orchestration support durable state for long-running tasks?

Yes, tmux-based orchestration provides durable state for long-running tasks by using tmux panes and a shared state store to maintain reliable progress tracking across team members.

Can I manage agent lifecycles and worker inboxes via CLI commands?

Yes, the OMX toolset provides API-driven mutations and CLI-driven commands to manage task lifecycles, worker inboxes, and status visibility for coordinated multi-agent sessions.

How do I start a coordinated team session with multiple agents?

Start a coordinated team session by running `omx team <N:agent-type> "<task description>"`, then monitor the parallel workstreams with `omx team status` until the task is complete.

When should I use multi-agent orchestration for my workflow?

Use multi-agent orchestration for long-running workflows requiring auditable startup and shutdown evidence, such as parallel data processing, evaluation tasks, or multi-step processes needing durable state.