internal-eval-run

Orchestrate isolated inner-pipeline eval runs with concurrency and structured JSON reporting.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill internal-eval-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: internal-eval-run
Source: https://github.com/paulingham/.claude/tree/main/skills/internal-eval/run
Command: npx skills add https://github.com/paulingham/.claude --skill internal-eval-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated, isolated execution of inner pipelines per evaluation case, ensuring outer state remains untouched while capturing verdicts, duration, and costs.

Core Features & Use Cases

  • Isolation-first orchestration: launches inner pipelines under a shadow environment with dedicated harness pinning to prevent cross-case contamination.
  • Concurrency and scale: supports suite-level concurrency, resumable runs, and result aggregation to evaluate large case sets efficiently.
  • Structured reporting: outputs per-case result.json and suite aggregates to drive downstream scoring and learnings.

Quick Start

Run the internal-eval-run skill to execute one case through the inner pipeline in isolation.

Frequently Asked Questions about internal-eval-run

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

FAQPage Schema
How do I run isolated evaluation pipelines without cross-case contamination?

Isolated evaluation pipelines run each case under a shadow environment with dedicated harness pinning to prevent cross-case contamination. This ensures outer state remains untouched while executing inner pipelines per case.

Can I resume an interrupted evaluation suite run across many cases?

Yes, evaluation suite orchestration supports resumable runs. It applies concurrency and result aggregation to scale evaluation across large case sets efficiently, capturing verdicts, duration, and cost traces.

How does structured JSON reporting work for automated evaluation harnesses?

Structured JSON reporting outputs per-case result.json files and suite-level aggregates. These reports capture verdicts, duration, and cost traces to drive downstream scoring and learning analysis.

What's the best way to orchestrate concurrent inner pipeline runs for large evaluation suites?

Suite-level orchestration applies concurrency to inner pipeline runs, enabling efficient scaling across large case sets. It satisfies environment isolation contracts, harness pinning, and timeouts while aggregating results.

Does the evaluation harness enforce timeouts and environment isolation contracts per case?

Yes, isolated inner-pipeline orchestration enforces environment isolation contracts, harness pinning, and timeouts per case. This guarantees each evaluation runs independently without affecting outer state or other cases.

Why does my inner pipeline evaluation lose state between concurrent test cases?

Cross-case state loss occurs without shadow environment isolation. Running inner pipelines under dedicated harness pinning per case prevents contamination, keeping each evaluation case fully independent and isolated.