Pilot result evaluation

Evaluate pilot experiment results and classify outcomes as pass, fail, or inconclusive.

Updated May 23, 2026
One-click install
npx skills add https://github.com/duany049/skill-runtime-evolution --skill pilot-result-evaluation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pilot result evaluation
Source: https://github.com/duany049/skill-runtime-evolution/tree/main/i18n/en/skills/exp-pilot-eval
Command: npx skills add https://github.com/duany049/skill-runtime-evolution --skill pilot-result-evaluation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents ambiguous pilot outcomes from lingering by turning noisy pilot runs into a clear verdict and consistently updating the corresponding idea page.

Core Features & Use Cases

  • Verdict evaluation: Reads pilot results and log, then applies success-criterion logic to classify outcomes as pass, fail, or inconclusive.
  • Wiki state update: Writes back to the idea page fields including pilot_result, failure_reason (when failed), and status transitions to failed when required.
  • Persistent reporting: Generates and saves a PILOT_VERDICT_REPORT summarizing metrics, log signals, and next-step guidance.

Quick Start

Run the pilot evaluation for a specific idea slug so the system updates wiki/ideas/{slug}.md and produces a PILOT_VERDICT_REPORT from the pilot artifacts.

Frequently Asked Questions about Pilot result evaluation

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

FAQPage Schema
How do I evaluate pilot experiment results and update my wiki idea page?

To evaluate pilot experiment results, this skill reads seed result JSON files and pilot logs, computes metric summaries against baselines, and writes the verdict directly into your wiki idea metadata fields.

How does pilot evaluation classify experiment outcomes as pass, fail, or inconclusive?

Pilot evaluation classifies experiment outcomes by applying success-criterion logic to your metric summaries and pilot log signals, producing a clear pass, fail, or inconclusive verdict for your idea page.

What is the best way to automate wiki status lifecycle updates after a pilot run?

Automating wiki status lifecycle updates requires applying forward-only lifecycle rules to transition idea page fields, setting pilot_result, logging failure_reason, and moving status to failed when criteria are not met.

How do I generate a persistent report summarizing pilot metrics and log signals?

You can generate a persistent report by running the evaluation against a specific idea slug, which computes metric comparisons and saves a PILOT_VERDICT_REPORT summarizing metrics, log signals, and next-step guidance.

Can I use this pilot evaluation without manually checking baseline metrics for my research automation workflow?

Yes, you can use this for research automation without manual baseline checks because the system automatically loads the pilot spec, computes metric summaries against defined baselines, and applies the success criteria autonomously.

Why does my pilot evaluation result remain inconclusive despite having experiment logs?

Pilot evaluation results remain inconclusive when the extracted log signals and computed metric summaries do not clearly meet or violate the defined success criteria, preventing a definitive pass or fail wiki update.