zicato-author-board

Author and validate zicato board.jsonl evaluation contracts for multi-agent harness testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create and maintain zicato board.jsonl files without violating the evaluation contract or introducing invalid task, expectation, judge, or emulator configurations.

Core Features & Use Cases

  • Board Authoring: Define single-turn, scripted multi-turn, and emulated multi-turn evaluation entries with stable identifiers, budgets, tags, context, and weights.
  • Outcome and Process Checks: Configure one expectation per entry using predicates, text, regex, JSON Schema, or rubrics, alongside inline or Python process judges.
  • Validation and Safety: Apply board metadata, drift controls, continuous scoring, emulator callable separation, and mid-epoch protection when evolving a zicato target.
  • Use Case: Add a stakeholder-dialogue task that checks whether an agent incorporates feedback without fabricating metrics, then validate the board before starting a new evaluation epoch.

Quick Start

Use this Skill to add or revise a zicato board entry for a new agent evaluation scenario and verify that its schema, expectations, judges, and emulator configuration are valid.

Frequently Asked Questions about zicato-author-board

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

FAQPage Schema
How do I create a multi-agent evaluation board with drift detection and process judges?

To create a multi-agent evaluation board with drift detection and process judges, author a zicato board.jsonl file defining entries with stable identifiers, valid expectation fields, supported DriftKind tokens, and inline or Python process judges.

What is a zicato board.jsonl evaluation contract used for?

A zicato board.jsonl evaluation contract defines single-turn tasks, scripted or emulated multi-turn conversations, outcome expectations, process judges, drift controls, and continuous scores for reliable multi-agent harness testing.

How do I configure emulated multi-turn conversations in an evaluation harness?

To configure emulated multi-turn conversations in an evaluation harness, define board entries with distinct auxiliary and harness callables for emulated users, ensuring strict separation between them to maintain evaluation contract validity.

Can I use regex and JSON Schema for agent outcome expectations in test authoring?

Yes, you can use regex and JSON Schema for agent outcome expectations in test authoring. A zicato board entry accepts one expectation per entry configured via predicates, text, regex, JSON Schema, or rubrics.

Why does my zicato board validation fail when adding new evaluation entries?

Zicato board validation fails when entries violate the evaluation contract by introducing invalid task configurations, unsupported DriftKind tokens, missing stable identifiers, or invalid expectation and judge fields.

What's the best way to maintain evaluation boards across testing epochs without drift?

To maintain evaluation boards across testing epochs without drift, apply epoch-safe board maintenance practices including mid-epoch protection, drift controls, and continuous scoring validation before starting a new evaluation epoch.