plaited/agent-eval-harness · Archived

compare-trials

Analyze graded `trial_result` JSONL outputs from the eval pipeline, including reliability and custom slicing.

First seen Jun 17, 2026

Installation

$ npx skills add plaited/agent-eval-harness --skill compare-trials

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from plaited/agent-eval-harness · top by installs.

npx skills add plaited/agent-eval-harness

Browse all from plaited/agent-eval-harness

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseISC

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,272 B
  • docs SUMMARY.md 131 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Compare Trials

Use this skill for analysis over graded JSONL outputs, typically after:

agent-eval-harness eval '{"mode":"grade",...}' > graded.jsonl

Default path

For normal baseline-vs-challenger comparisons, use:

agent-eval-harness eval '{"mode":"compare",...}'

Use custom scripts only when suite-specific analysis is required.

Custom analysis use cases

  • cost analysis
  • token usage analysis
  • slices by task metadata (category, difficulty, source)
  • custom regression gates
  • per-agent metadata summaries

Script guidance

When writing a custom script:

  1. Parse JSONL rows as trial_result.
  2. Validate graded rows (pass and score non-null).
  3. Group by stable identity fields (taskId, trialIndex, runId).
  4. Separate:

- standalone run metrics - comparable-overlap metrics

  1. Report uncertainty where possible (bootstrap confidence intervals).
  2. Use exactPassAtK naming for combinatorics-based pass@k metrics (do not label exact values as estimatedPassAtK).

Reference helpers remain in references/ for bootstrap/statistics utilities.