eval-validity-review

Review an Inspect AI evaluation's claims, naming, dataset, and scoring validity.

657|419|Updated Oct 2, 2024
One-click install
npx skills add https://github.com/UKGovernmentBEIS/inspect_evals --skill eval-validity-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-validity-review
Source: https://github.com/UKGovernmentBEIS/inspect_evals/tree/main/.claude/skills/eval-validity-review
Command: npx skills add https://github.com/UKGovernmentBEIS/inspect_evals --skill eval-validity-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluations in the inspect_evals repository may make false claims about their data provenance, use misleading names, contain samples that cannot be both passed and failed, or score proxies instead of ground truth. This Skill provides a structured, read-only review process that determines whether an evaluation actually measures what it claims to measure.

Core Features & Use Cases

  • Claims Coherence Verification: Extracts every verifiable claim from the README, eval.yaml, docstrings, and dataset, then checks each against the actual code and data, flagging fabricated provenance or false mechanism claims.
  • Name, Dataset, and Scoring Validity Checks: Assesses whether the eval name matches its real scope, whether models can both succeed and fail given available tools and sandbox affordances, and whether the scorer measures ground truth rather than weak proxies like substring matching.
  • Structured Report Generation: Produces a VALIDITY_REPORT.md with an overall rating (Valid, Valid with Minor Issues, Validity Concerns, or Significant Validity Issues), severity-tagged findings, and prioritized recommendations.
  • Use Case: Before merging a community-contributed evaluation into inspect_evals, run this review to confirm its HuggingFace dataset claims are real, its sandbox tasks are solvable, and its LLM-judge scorer verifies actual task completion.

Quick Start

Ask the AI to review the validity of the evaluation in src/inspect_evals/<eval_name> and generate a validity report.

Frequently Asked Questions about eval-validity-review

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

FAQPage Schema
How do I check if an Inspect AI evaluation is valid?

Run this review on the evaluation's folder under src/inspect_evals/. It reads the task definition, dataset loader, scorer, README, and eval.yaml, then verifies claims, name accuracy, dataset feasibility, and scoring alignment, producing a VALIDITY_REPORT.md with an overall rating.

What does the evaluation validity review check?

It checks four dimensions: claims coherence (whether stated data provenance and mechanisms hold up), name validity (whether the name matches the actual scope), dataset validity (whether models can both succeed and fail), and scoring validity (whether the scorer measures ground truth rather than proxies).

Does the validity review modify my evaluation code?

No, the review is strictly read-only. It records observations in a NOTES.md file and produces a VALIDITY_REPORT.md under agent_artefacts/, but never changes the evaluation's source code, dataset, or configuration.

When should I use eval-validity-review instead of code quality checks?

Use it when you need to know whether an evaluation measures what it claims to measure, such as before merging a community submission. For code quality or test coverage concerns, use the eval-quality-workflow or ensure-test-coverage skills instead, as stated in the skill description.

What are common validity problems in LLM evaluations?

Common issues include fabricated data provenance (inline samples claimed to come from HuggingFace), impossible success (tasks referencing nonexistent sandbox resources), unverifiable compliance in safety evals, and scorers using substring matching as a weak proxy for natural language outcomes.