zicato-audit-board

Audit zicato evaluation boards for harness correctness using canonical artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects evaluation-harness defects that can produce misleading zicato verdicts, including unwinnable ground truth, proxy-graded outputs, dead judges, inverted scoring, and nondeterministic results.

Core Features & Use Cases

  • Known Baseline Validation: Compare trivially correct and trivially wrong stubs to verify that board expectations behave as intended.
  • Harness Mechanics Audit: Check ground-truth winnability, graded-artifact fidelity, judge-fire counts, scalar arithmetic, ranking direction, determinism, and monotonicity scope.
  • Telemetry-Based Diagnostics: Inspect loss profiles, generation scores, board declarations, event streams, and health findings to identify structural evaluation problems before tournaments or evolution.
  • Use Case: After changing a zicato board, audit a deterministic baseline run to confirm that real agent outputs are graded, every declared judge fires, and better candidates receive the intended scalar ranking.

Quick Start

Use the zicato audit board skill to inspect the existing baseline run artifacts and determine whether the board can be trusted for tournament or evolution decisions.

Frequently Asked Questions about zicato-audit-board

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

FAQPage Schema
How do I validate evaluation harness correctness before running a tournament?

You validate evaluation harness correctness by checking ground-truth winnability, graded-artifact fidelity, and judge-fire counts against baseline run artifacts. This verifies expectations behave as intended and catches unwinnable ground truth or dead judges.

Why does my evaluation harness produce nondeterministic results or misleading verdicts?

Nondeterministic results and misleading verdicts stem from harness defects like proxy-graded outputs or inverted scoring. Inspect loss profiles, event streams, and board declarations to isolate structural evaluation problems before tournaments.

What is ground-truth winnability checking in an evaluation harness?

Ground-truth winnability checking verifies that trivially correct stubs pass and trivially wrong stubs fail. It confirms board expectations behave as intended, ensuring the evaluation harness can actually grade real agent outputs correctly.

How do I check if every declared judge fires during an evaluation run?

You check if every declared judge fires by auditing judge-fire counts using canonical board and event artifacts. This harness mechanics audit confirms all declared judges execute as intended during the evaluation run.

When do I need to run an evaluation board audit?

Run an evaluation board audit after building or changing boards and whenever verdicts, pass rates, judge behavior, or candidate rankings appear suspicious. This ensures the board can be trusted for tournament or evolution decisions.

How do I verify pass-rate monotonicity and determinism in telemetry diagnostics?

Verify pass-rate monotonicity and determinism by inspecting telemetry artifacts including loss profiles, generation scores, and event streams. This identifies nondeterministic results and inverted scoring, ensuring better candidates receive the intended scalar ranking.