multi-agent-orchestrator

Coordinate parallel CLI agents to evaluate competing solutions and declare a winner.

10|3|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/tekliner/improvado-agentic-frameworks-and-skills --skill multi-agent-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent-orchestrator
Source: https://github.com/tekliner/improvado-agentic-frameworks-and-skills/tree/main/skills/multi-agent-orchestrator
Command: npx skills add https://github.com/tekliner/improvado-agentic-frameworks-and-skills --skill multi-agent-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Python 3.8+, Claude Code CLI, Codex CLI, Gemini CLI, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tackles highly complex tasks where a single AI agent might struggle or where the optimal solution is unknown. It automates the process of comparing multiple AI agents' approaches, ensuring you get the best possible outcome for high-stakes problems.

Core Features & Use Cases

  • Parallel Agent Execution: Simultaneously runs multiple CLI agents (Claude Code, Codex, Gemini) on the same task.
  • Objective Self-Evaluation: Agents evaluate their own performance against user-defined, measurable success criteria.
  • Automated Winner Selection: Identifies the best-performing agent based on objective metrics, eliminating subjective bias.
  • Artifact Placement Enforcement: Ensures all agent outputs are neatly organized within their dedicated workspaces for easy comparison and traceability.
  • Use Case: You need to implement an "optimal customer segmentation algorithm" for a critical business decision. Instead of relying on one agent, you use this skill to launch Claude Code, Codex, and Gemini in parallel. They each propose and implement a solution, self-evaluate against criteria like "process 1M rows in <5s" and "memory usage <500MB", and the skill declares the winner, providing you with the most efficient algorithm.

Quick Start

When facing a complex task (e.g., "Implement optimal customer segmentation algorithm"), first agree on a task folder location with Claude. Claude will then create a draft task file for you to edit. Once you confirm "Ready", Claude will launch the agents in parallel to find the best solution.

Frequently Asked Questions about multi-agent-orchestrator

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

FAQPage Schema
How do I compare multiple AI agents solving the same complex task?

Multi-agent orchestration runs Claude Code, Codex, and Gemini in parallel on identical tasks, each generating independent solutions. Each agent self-evaluates against your predefined success criteria, and the system declares a winner based on objective metrics rather than subjective judgment.

When should I use multiple agents instead of a single AI solution?

Use multi-agent orchestration for high-complexity tasks (above 7/10 difficulty) where the optimal approach is unclear or multiple viable implementations exist. It eliminates uncertainty by comparing competing solutions with measurable, data-driven evaluation.

How do I set up and run parallel agent execution?

Define a task file with your problem statement and success criteria in a shared folder. Each agent (Claude Code, Codex, Gemini) receives the same task, works in isolated workspaces, implements a solution, and scores itself. The orchestrator aggregates results and identifies the best performer.

What evaluation criteria can I use to pick the winning agent solution?

You define measurable success criteria relevant to your task—such as performance benchmarks (runtime, memory usage), accuracy thresholds, code quality metrics, or business outcomes. Each agent self-evaluates against these criteria; the orchestrator selects the winner based on aggregated scores.

Can I use this with cloud-based AI services or only local agents?

The Skill orchestrates CLI agents—Claude Code, Codex, and Gemini—each of which connects to their respective backends. Each agent's capabilities and API integrations are determined by that CLI's own configuration and dependencies.