What problem does it solve?
Benchmarking a document extraction library requires trustworthy ground truth, reproducible runs, and careful diagnosis of failures. This Skill guides you through running, diagnosing, and changing the Xberg benchmark harness without corrupting ground truth or misreading results.
Core Features & Use Cases
- Ground-Truth Integrity: Enforces independently sourced ground truth (manual, vision, pdf_text_layer, pandoc, python-docx) recorded in each fixture's
ground_truth.source field, never Xberg's own extractor output.
- Run Diagnosis: Separates infrastructure failures (missing backends, absent fixtures, malformed artifacts) from genuine extraction or quality regressions, and inspects per-adapter artifacts before aggregate jobs.
- Fair A/B Comparison: Requires identical corpus, config, renderer, cache state, and metric on control and experiment, with extraction and OCR caches invalidated before behavior-changing runs.
- Use Case: Before dispatching the dispatch-only
.github/workflows/benchmarks.yaml workflow, validate fixtures with the harness validate-gt command and add focused tests for any report or artifact contract changes.
Quick Start
Diagnose why the latest benchmark run shows a quality regression for the PDF adapter before dispatching a new workflow run.