eval-report-workflow

Generates reproducible LLM evaluation reports with model selection, cost estimation, and results tables.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating a credible evaluation report for an Inspect AI eval requires selecting suitable models, estimating compute costs, running evaluations within a budget, and formatting results consistently. This Skill automates that entire workflow so contributors can produce standardized, reproducible reports for the inspect_evals repository.

Core Features & Use Cases

  • Model Selection & Cost Estimation: Picks paper-relevant or frontier models from multiple providers and estimates token usage and dollar cost from a small pilot run, capped at $5 per model.
  • Automated Report Generation: Drives tools/evaluation_report.py to produce a report.md with results tables, reference comparisons, per-category breakdowns, token totals, and reproducibility metadata.
  • Register Integration: Populates the evaluation_report block in eval.yaml for register entries and commits report_config.yaml, report.md, and results/ alongside the eval.
  • Use Case: A contributor adding a new benchmark to inspect_evals asks the agent to run the evaluation report workflow; it runs a 5-sample pilot, recommends three models across providers with a cost estimate, then generates and splices the final report into the README.

Quick Start

Ask the agent to make an evaluation report for a specific eval, for example: run the Make An Evaluation Report workflow for the gpqa eval.

Frequently Asked Questions about eval-report-workflow

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

FAQPage Schema
How do I create an evaluation report for an inspect_evals benchmark?

Run the Make An Evaluation Report workflow, which performs a small pilot run to estimate tokens, selects suitable models, and drives tools/evaluation_report.py with a report_config.yaml. The script writes report.md and header-only JSON logs under the eval's results/ folder.

How are models selected for an Inspect AI evaluation report?

Models are chosen from the eval's arXiv paper when available, aiming for three candidates across at least two providers. Remaining slots are filled with frontier models listed in references/frontier-models.md, with prices verified via the LLM prices API.

How much does running an evaluation report cost?

The workflow targets the full dataset or $5 of compute per model, whichever is cheaper. Cost is estimated from a 5-sample pilot run using the most expensive model, and Gemini reasoning models are assumed to use roughly 10x the tokens.

Can I add an evaluation report to a register entry instead of a README?

Yes. For register entries, populate the evaluation_report block in eval.yaml with timestamp, results, and notes instead of editing README.md directly. The README is regenerated from the YAML by running make check.

What happens if the sample size is too small for a meaningful evaluation?

If the $5-per-model budget yields fewer than 20 samples or fewer than three times the meaningful subcategories, the workflow warns that results will not be statistically meaningful. It then suggests requesting additional testing resources from the repository maintainers.