audit-benchmark-evidence

Audit benchmark validity, reproducibility, and evidence claims from raw artifacts.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/standardbeagle/lci-cpp --skill audit-benchmark-evidence-standardbeagle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-benchmark-evidence
Source: https://github.com/standardbeagle/lci-cpp/tree/main/.agents/skills/audit-benchmark-evidence
Command: npx skills add https://github.com/standardbeagle/lci-cpp --skill audit-benchmark-evidence-standardbeagle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Benchmarks, A/B tests, and model evaluations often contain hidden defects—prompt leakage, unequal arms, post-hoc analysis, or pooled results that hide failures—yet their reports look convincing. This Skill audits the raw artifacts behind any benchmark claim and produces a fail-closed verdict grounded in evidence rather than the author's conclusions. ## Core Features & Use Cases - Twelve hard validity gates: Scores preregistration, treatment isolation, prompt neutrality, leakage, oracle independence, grid integrity, exclusion handling, controls, variance, stratification, reproducibility, and claim scope as pass, fail, inconclusive, or not_applicable. - Fail-closed scoring script: Validates structured gate data with scripts/score_audit.py and derives the overall outcome so one failed hard gate overrides many passing checks. - Structured audit report: Generates a report from references/report-template.md covering recomputed effects, blockers with bias direction, claim-by-claim support, and residual uncertainty. - Use Case: A team claims their new prompting strategy beats the baseline in an A/B evaluation. Use this Skill to recompute per-stratum effects, check for answer leakage in model-visible prompts, verify the oracle rejects wrong answers, and determine whether the headline claim survives. ## Quick Start Use the audit-benchmark-evidence skill to audit this benchmark's raw results, prompts, and analysis code and grade whether its claims are supported.

Frequently Asked Questions about audit-benchmark-evidence

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

FAQPage Schema
How do I audit whether a benchmark result is valid?▼

Audit benchmark validity by working from raw artifacts: inventory the preregistration, prompts, oracle, and raw results, then score twelve hard gates covering leakage, arm equivalence, oracle independence, and reproducibility. The outcome is fail-closed, so missing evidence yields inconclusive rather than pass.

How to detect answer leakage in an LLM evaluation?▼

Detect answer leakage by inspecting model-visible inputs for oracle wording, solution identifiers, hidden paths, grader tokens, and cross-cell state. Gate G4 treats any plausible leakage as critical unless bounded evidence proves it unreachable.

What makes an A/B test comparison fair?▼

A fair A/B comparison requires identical tasks, facts, context, tools, time, and grading except for the declared treatment. Undeclared differences such as extra facts, favorable labels, or unequal affordances fail the treatment isolation and prompt neutrality gates.

Can I use this for model evaluation reports without raw data?▼

No, the audit requires raw artifacts including immutable revisions, fixtures, raw results, and analysis code. When required evidence is unavailable, the Skill returns inconclusive rather than inferring a pass from a polished report or green tests.

Why does a single failed gate fail the whole benchmark audit?▼

The rubric forbids averaging scores because one hard validity failure, such as contamination or outcome-dependent analysis, can invalidate the entire experiment. The scoring script derives fail whenever any hard gate fails, regardless of how many other gates pass.

When should a benchmark recommendation go to production?▼

Recommend production change only when every relevant hard gate passes, the effect exceeds preregistered noise and practical thresholds, the tested arm is production-faithful, and residual uncertainty plus the next live validation step are stated.