team

Orchestrate multi-agent OMX teams across tmux-powered workers with state management.

1|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/prthik/prathik-astro --skill team-prthik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/prthik/prathik-astro/tree/main/.codex/skills/team
Command: npx skills add https://github.com/prthik/prathik-astro --skill team-prthik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX teams require coordinated execution across multiple workers and tmux panes, with durable state and controlled messaging to avoid drift and fragmentation.

Core Features & Use Cases

  • Orchestrates leader-worker coordination, task dispatch, and state management for multi-agent workflows.
  • Supports long-running parallel executions with tmux-based worker panes and mailbox-based messaging.
  • Use cases include scalable experimentation, batch task processing, and robust workflow orchestration in development and production.

Quick Start

Launch a coordinated OMX team workflow with a leader and N workers using the omx team command.

Frequently Asked Questions about team

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

FAQPage Schema
How do I coordinate multi-agent OMX teams with durable state across tmux workers?

Multi-agent OMX team orchestration is automated across tmux-powered workers using a leader-worker model with mailbox-based messaging. This provides durable state management and controlled messaging to prevent drift in long-running parallel workflows.

What is the best way to manage parallel task execution and prevent workflow fragmentation?

Parallel task execution is managed through a coordinated leader-worker dispatch system with tmux-based worker panes. Mailbox-based messaging controls inter-agent communication, ensuring durable state and preventing fragmentation during long-running executions.

How do I set up a runtime lifecycle for OMX workflows with resume and shutdown commands?

The OMX workflow lifecycle is set up using a SKILL.md frontmatter defining name and description, alongside optional scripts and assets. A defined runtime lifecycle is required with status, resume, and shutdown commands for end-to-end operation.

Does tmux support long-running parallel batch processing for multi-agent development workflows?

Tmux supports long-running parallel batch processing by powering dedicated worker panes for multi-agent workflows. This configuration enables scalable experimentation and robust task orchestration in both development and production environments.

Can I use mailbox-based messaging for inter-agent communication in scalable experimentation workflows?

Mailbox-based messaging is supported for inter-agent communication within scalable experimentation workflows. It controls message delivery across tmux-powered workers to maintain state consistency and prevent drift during coordinated task execution.

Why do I need a defined runtime lifecycle for parallel execution and state management?

A defined runtime lifecycle is needed for parallel execution to provide reliable status tracking, resume capabilities, and shutdown commands. This ensures durable state management and controlled messaging across tmux workers throughout end-to-end operation.