zicato-build-board

Design evaluation boards for multi-agent harnesses with judges and holdout splits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps operators turn vague quality goals into discriminating evaluation boards that reliably distinguish stronger and weaker multi-agent harnesses while avoiding overfitting and noisy signals.

Core Features & Use Cases

  • Board Entry Design: Create single-turn, scripted multi-turn, and emulated multi-turn tasks with expectations, tags, weights, and holdout coverage.
  • Judge and Loss Configuration: Declare process judges, select the correct telemetry source, and tune drift, pass-rate, severity, per-kind, per-judge, runtime, and namespace weights.
  • Validation and Safe Application: Build changes as a draft, preview validation warnings, configure train and holdout slices, and apply the completed board only after explicit confirmation.
  • Use Case: Help an operator build a board that measures both final-answer correctness and tool-use quality, emphasizes off-topic drift, protects passing entries with monotonicity, and reserves part of the board for generalization checks.

Quick Start

Use the zicato board-building skill to draft and validate a holdout-aware evaluation board with entries, judges, and loss weights for the target agent behavior.

Frequently Asked Questions about zicato-build-board

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

FAQPage Schema
How do I design evaluation boards for multi-agent systems that prevent overfitting?

Evaluation boards prevent overfitting by reserving holdout splits for generalization checks, applying monotonicity protections to passing entries, and requiring explicit confirmation before rolling a new evaluation epoch.

How do I configure process judges and weighted loss for multi-agent harness evaluation?

Configure process judges by selecting telemetry sources and tuning drift, pass-rate, severity, per-kind, per-judge, runtime, and namespace weights to build a weighted loss profile that grades observable multi-agent behavior.

How do I validate evaluation board changes before applying them to a multi-agent harness?

Validate evaluation board changes by building drafts, previewing validation warnings, configuring train and holdout slices, and applying the board only after explicit confirmation to prevent noisy signals.

Does multi-agent evaluation board design require explicit collusion prevention safeguards?

Multi-agent evaluation board design requires explicit collusion prevention safeguards, observable telemetry grading, and validation checks to ensure process judges reliably distinguish stronger and weaker harnesses.

What is the best way to measure both final-answer correctness and tool-use quality in multi-agent systems?

Measure final-answer correctness and tool-use quality by creating board entries with expectations, tags, and weights, then assigning process judges to monitor off-topic drift and tool telemetry.

Can I use single-turn and emulated multi-turn tasks in the same evaluation board?

You can combine single-turn, scripted multi-turn, and emulated multi-turn tasks in the same evaluation board by assigning each entry specific expectations, tags, weights, and holdout coverage.