experiment-audit

Verify ground-truth provenance, metric normalization, and result-file claims in experiment repositories.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill experiment-audit-raja21068
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-audit
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/experiment-audit
Command: npx skills add https://github.com/raja21068/AutoResearch --skill experiment-audit-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Experiment-audit prevents overconfident or incorrect research claims by checking whether reported results are grounded, correctly computed, and actually supported by the underlying files.

Core Features & Use Cases

  • Ground-truth provenance verification: Confirms evaluation targets are sourced from datasets rather than being derived from model outputs without explicit proxy labeling.
  • Score normalization fraud detection: Flags suspicious metric normalization that divides by model-derived maxima/minima/means.
  • Result-to-claim existence and consistency checks: Verifies that paper/narrative claims reference real result files with matching metric keys and values.
  • Dead code and scope assessment: Warns when metric functions are never called or when evaluation coverage is too small for the strength of claims.
  • Cross-model integrity review: Separates collection (executor) from judgment (reviewer) to reduce bias and improve audit reliability.

Quick Start

Run experiment-audit on your completed experiment directory by providing the path to the experiment results so it generates EXPERIMENT_AUDIT.md and EXPERIMENT_AUDIT.json.

Frequently Asked Questions about experiment-audit

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

FAQPage Schema
How do I verify research reproducibility and validate experiment results before publication?

To verify research reproducibility, you can audit experiment integrity by checking ground-truth provenance, metric normalization validity, and result-file existence against repository artifacts. This prevents overconfident claims by ensuring reported results are correctly computed and grounded.

How do I detect metric normalization fraud in model evaluation pipelines?

To detect metric normalization fraud, audit your evaluation pipeline to flag suspicious score normalizations that divide by model-derived maxima, minima, or means. This ensures metrics are grounded in dataset values rather than manipulated model outputs.

How do I check if paper claims match actual result files in my repository?

To check if paper claims match actual result files, perform a result-to-claim consistency audit that verifies narrative performance claims reference real result files with matching metric keys and values. This validates that claims are supported by underlying artifacts.

What is ground truth provenance verification for machine learning experiments?

Ground truth provenance verification confirms that evaluation targets are sourced from datasets rather than derived from model outputs without explicit proxy labeling. This maintains experiment integrity by validating the source of your evaluation benchmarks.

How do I audit experiment integrity for dead code and insufficient evaluation coverage?

To audit experiment integrity for dead code and insufficient coverage, assess metric function call frequency and evaluation scope against claim strength. This warns when metric functions are never called or when coverage is too small for the claims made.

Can I use an automated reviewer to reduce bias when auditing model performance claims?

Yes, you can reduce bias when auditing model performance claims by separating collection from judgment using an executor to gather file paths and a separate read-only reviewer to produce an integrity verdict. This cross-model approach improves audit reliability.