research.cross.compare

Compares primary metrics across multiple research projects with statistical tests and generates comparison reports.

Updated May 9, 2026
One-click install
npx skills add https://github.com/0h-n0/auto-research --skill research-cross-compare-0h-n0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research.cross.compare
Source: https://github.com/0h-n0/auto-research/tree/main/skills/research.cross.compare
Command: npx skills add https://github.com/0h-n0/auto-research --skill research-cross-compare-0h-n0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, scipy, pandas, matplotlib, seaborn, and includes references (resource) components.

What problem does it solve? When running multiple related LLM research projects (e.g., baseline vs. improved variants), results live in separate .research/<slug>/ directories, making rigorous cross-project comparison manual and error-prone. This Skill aggregates succeeded run metrics and produces a statistically sound comparison report. ## Core Features & Use Cases - Metric Aggregation: Collects primary metric values from 06_RUNS/*/metrics.json across two or more projects, excluding failed runs, into a reproducible raw.json. - Statistical Testing: Runs paired bootstrap (B=10000) or Welch's t-test per project pair, with Cohen's d, Cliff's delta effect sizes, and Holm-Bonferroni multiple-comparison correction. - Report & Figures: Generates REPORT.md with ranking tables and pairwise results, plus boxplot and effect-size PDF figures via matplotlib/seaborn. - Use Case: Compare an MMLU baseline project against a chain-of-thought variant to determine whether the accuracy improvement is statistically significant before writing it up in a paper. ## Quick Start Use the research.cross.compare skill to compare the projects llm-eval-mmlu-baseline and llm-eval-mmlu-cot on their primary metric with statistical tests.

Frequently Asked Questions about research.cross.compare

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

FAQPage Schema
How do I statistically compare results across multiple ML experiments?▼

Aggregate the metric values from each experiment's runs, then apply paired bootstrap when runs share seeds or Welch's t-test otherwise. This Skill automates that workflow, adding Cohen's d and Cliff's delta effect sizes plus Holm-Bonferroni correction across all project pairs.

How to compare baseline vs improved model runs with significance testing?▼

Provide the slugs of both projects; the Skill reads succeeded runs from each project's 06_RUNS directory, computes mean differences with 95% confidence intervals, and reports Holm-corrected p-values in a REPORT.md ranking table.

What is the difference between paired bootstrap and Welch's t-test?▼

Paired bootstrap resamples paired differences and is used when runs share the same seeds; Welch's t-test handles unpaired samples with unequal variances. The Skill selects paired bootstrap when run counts align, otherwise falls back to Welch's t-test.

Can I compare projects that use different metric names?▼

No. The Skill does not normalize across different metric names and exits with an error if the compared projects use mismatched metrics. All compared projects must report the same common metric.

What happens to failed runs during comparison?▼

Failed runs are excluded from aggregation, but their count is recorded in the report's exclusions section. Projects with zero succeeded runs trigger a warning and are dropped from the aggregation.