finalize-run

Validate benchmark run data and save structured JSON output to a specified path.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/slabgorb/sidequest --skill finalize-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize-run
Source: https://github.com/slabgorb/sidequest/tree/main/.pennyfarthing/skills/pf-finalize-run
Command: npx skills add https://github.com/slabgorb/sidequest --skill finalize-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Benchmark runs often fail to enforce a consistent finalization step, risking unreliable results and audit gaps.

Core Features & Use Cases

  • Strict data validation for agent, judge, and score fields, including timestamp formats and token counts.
  • Guardrail enforcement ensuring every run passes through a single save point before results are stored.
  • Multi-judge support for relay-style evaluations with consistent score verification and timestamp sanity.

Quick Start

Invoke the finalize-run skill with a complete JSON payload to validate the run and write the results to the specified output path.

Frequently Asked Questions about finalize-run

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

FAQPage Schema
How do I validate benchmark run results and save structured JSON output?

To validate benchmark run results, you can enforce a single guardrail exit point that checks ISO8601 timestamps, required token counts, and score extraction before saving structured JSON output to a specified file path.

Can I use a validation guardrail for multi-judge relay benchmark scenarios?

Yes, multi-judge relay benchmark scenarios are supported. The validation guardrail enforces score verification and timestamp sanity checks across agent and judge inputs, ensuring consistent finalization for solo, duel, or relay runs.

What does timestamp sanity checking enforce during benchmark validation?

Timestamp sanity checking enforces strict ISO8601 timestamp formats for benchmark runs. This ensures chronological consistency across agent and judge inputs before results pass through the final save point.

How do I enforce required token counts in benchmark evaluation outputs?

You can enforce required token counts by passing a complete JSON payload through a validation guardrail. This verifies agent and judge token data alongside score extraction and timestamp formats before writing to an output path.

What's the best way to prevent audit gaps in benchmark run finalization?

The best way to prevent audit gaps is enforcing a single guardrail save point for benchmark runs. This validates all agent, judge, and score fields with timestamp sanity checks before storing structured JSON results.

Does benchmark validation work with duel scenarios and multiple judges?

Yes, benchmark validation works with duel scenarios and multiple judges. It enforces consistent score verification and timestamp sanity across all agent and judge inputs before finalizing structured JSON output.