zicato-configure-tournament

Configure zicato tournament brackets and multi-round evolution runs.

4|2|Updated May 14, 2026
One-click install
npx skills add https://github.com/pedapudi/zicato --skill zicato-configure-tournament
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zicato-configure-tournament
Source: https://github.com/pedapudi/zicato/tree/main/skills/zicato-configure-tournament
Command: npx skills add https://github.com/pedapudi/zicato --skill zicato-configure-tournament

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly configuration mistakes when setting up zicato tournaments and multi-round evolution runs, especially the confusion between within-round bracket structures and across-round evolution.

Core Features & Use Cases

  • Structure Selection: Choose among gauntlet, single-elimination, double-elimination, Swiss, and racing formats based on field size, noise, ranking needs, and budget.
  • Evolution Planning: Configure field size, replicates, rounds, promotion gates, cache modes, and runtime limits while understanding how proposer memory accumulates across rounds.
  • Validation and Cost Control: Estimate board-run costs, identify throttling and retry risks, and diagnose stalled evolution caused by missing experiment memory or non-persistent workspaces.
  • Use Case: When a multi-round run produces no promotions, use this Skill to determine whether the proposer is still learning from prior experiments and telemetry or whether the evolution loop is incorrectly configured.

Quick Start

Use the zicato tournament configuration skill to select an appropriate bracket, size a four-round evolution run, estimate its cost, and verify that experiment memory is being carried across rounds.

Frequently Asked Questions about zicato-configure-tournament

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

FAQPage Schema
How do I diagnose stalled evolution caused by missing experiment memory?

Diagnose stalled evolution by checking if the proposer still learns from prior experiments and telemetry. Missing memory often indicates non-persistent workspaces or incorrectly configured evolution loops.

Why does my multi-round tournament evolution produce no promotions across rounds?

Multi-round tournament evolution stalls when the proposer lacks experiment memory from prior rounds, often due to non-persistent workspaces. Verify that telemetry insights and proposer memory carry across rounds to restore promotion gates.

How do I select the right tournament bracket format for my multi-agent field size?

Select tournament brackets like gauntlet, single-elimination, double-elimination, Swiss, or racing based on your field size, noise levels, ranking needs, and budget constraints to ensure effective multi-agent evolution.

Do I need persistent workspaces to run multi-round evolution tournaments?

Tournament evolution requires persistent workspaces to ensure the proposer learns from prior experiments across rounds. Without persistent workspaces, experiment memory is lost and evolution stalls.

How do I estimate runtime and cost for a multi-round evolution tournament?

Estimate board-run costs by configuring field size, replicates, rounds, and runtime limits while selecting appropriate cache modes. This identifies throttling and retry risks before starting the evolution run.

What is the difference between within-round tournament brackets and across-round evolution?

Within-round tournament brackets structure single-round competition among agents, while across-round evolution uses proposer memory and promotion gates to advance winners through multiple persistent rounds.