skeptic-evaluate

Automate Skeptic evaluation cycles and render canonical evaluation artifacts.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Filivignaga/skeptic --skill skeptic-evaluate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skeptic-evaluate
Source: https://github.com/Filivignaga/skeptic/tree/main/codex/skeptic-evaluate
Command: npx skills add https://github.com/Filivignaga/skeptic --skill skeptic-evaluate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, auditable workflow to evaluate whether analysis outputs survive PCS checks appropriate to the active Skeptic route, and to generate the canonical evaluation artifacts that guide handoff to the next stage.

Core Features & Use Cases

  • Locks the evaluation plan from upstream contracts and renders cycle-by-cycle verdicts for stability, predictability, and validity.
  • Executes route-specific evaluation cycles (A through F) and produces artifacts such as 06_evaluation.yaml, 06_evaluation.py, and 06_evaluation.md.
  • Supports auto mode to run autonomous evaluation cycles and determine forward actions without interactive prompts.

Quick Start

Invoke skeptic-evaluate to run the evaluation cycles for your project and render the canonical evaluation YAML and report.

Frequently Asked Questions about skeptic-evaluate

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

FAQPage Schema
How do I automate PCS evaluation checks for reproducibility and provenance?

To automate PCS evaluation checks for reproducibility and provenance, this Skill locks the evaluation plan from upstream contracts and renders cycle-by-cycle verdicts for stability, predictability, and validity without interactive prompts.

What artifacts are generated when running route-specific evaluation cycles?

Running route-specific evaluation cycles generates canonical artifacts including 06_evaluation.yaml, 06_evaluation.py, and 06_evaluation.md to audit analysis claims and guide stage handoff.

How does YAML workflow audit enforce integrity checks for active analysis routes?

YAML workflow audit enforces integrity checks by requiring access to upstream contracts and prior stage outputs, verifying route-appropriate survival of analysis claims against PCS checks.

Do I need upstream contracts to run autonomous evaluation cycles?

Yes, you need upstream contracts and prior stage outputs to run autonomous evaluation cycles, as they are required to enforce reproducibility, provenance, and integrity checks for the active route.

Can I run evaluation cycles without interactive prompts to determine forward actions?

Yes, you can run evaluation cycles without interactive prompts using auto mode, which executes autonomous evaluation cycles and determines forward actions based on route-appropriate survival of analysis claims.