zicato-design-boards

Designs zicato evaluation boards that distinguish improved harnesses from challengers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps design zicato evaluation boards that produce meaningful score differences between champion and challenger harnesses, avoiding all-pass, all-fail, constant-drift, and non-differentiating evaluations.

Core Features & Use Cases

  • Behavioral Coverage: Select entries that exercise distinct regression-sensitive behaviors rather than repeating similar inputs.
  • Discriminating Evaluation: Tune expectations, continuous scores, weights, and sensitive-band difficulty so tournaments can identify genuine improvements.
  • Entry Strategy: Choose appropriately among single-turn, scripted multi-turn, and emulated multi-turn tests while accounting for cost, determinism, and emulator noise.
  • Board Controls: Apply board-wide drift suppression and judge-only evaluation appropriately, and prevent emulator collusion through distinct callables.
  • Use Case: When a zicato evolution loop runs successfully but promotes nothing, use this Skill to diagnose dead-weight entries and redesign the board around measurable behavior differences.

Quick Start

Ask the zicato board design skill to create a discriminating evaluation board for the harness behaviors you need to improve, including suitable entry types, expectations, weights, and drift settings.

Frequently Asked Questions about zicato-design-boards

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

FAQPage Schema
Why does my multi-agent evaluation tournament produce all-pass or non-differentiating scores?

Non-differentiating tournament scoring often stems from poorly designed evaluation boards that lack discriminating expectations or behavioral coverage. Redesigning the board with sensitive-band difficulty tuning and drift suppression ensures tournaments can identify genuine harness improvements.

How do I design evaluation boards that distinguish improved harnesses from unchanged challengers?

Design evaluation boards by selecting entries that exercise distinct regression-sensitive behaviors, tuning continuous scores and weights, and applying board-wide drift suppression. Grounding expectations in real outputs or tool-call ledgers ensures score differences reflect genuine harness improvements.

When should I use single-turn versus emulated multi-turn tests for behavioral testing?

Choose single-turn tests for deterministic, low-cost behavioral coverage, scripted multi-turn for controlled process evaluation, and emulated multi-turn when testing complex multi-agent systems. Account for emulator noise and prevent callable collusion by using distinct callables in emulator configurations.

How do I diagnose promotion failures when my evaluation loop runs but promotes nothing?

Diagnose promotion failures by identifying dead-weight entries that fail to distinguish champion from challenger harnesses. Redesign the evaluation board around measurable behavior differences using outcome and process evaluation, scoring sensitivity, and multi-turn test selection.

Can I apply drift detection configuration to prevent emulator collusion in multi-agent systems?

Yes, drift detection configuration can be applied at the board level alongside judge-only evaluation. Prevent emulator collusion by configuring distinct callables within the emulator, ensuring that multi-agent systems cannot artificially inflate tournament scores.