Compare published benchmark results
Compare published held-out evaluation observations from a public run, preserving the set, checkpoint, sample count and comparison limits.
What you get
A benchmark comparison with explicit coordinate, provenance and comparability limits.
Documented public read workflow; stored availability, source freshness and metric qualification still apply.
| Support | Requirement |
|---|---|
| Interfaces | CLI, MCP, HTTP |
| Access | public read |
| Workflow state | available |
| Credential corridors (see workflow) | None |
Ask your assistant
Example task
How did the published benchmark results change from the baseline?Install this skill
Use an existing compatible MCP connection or the customer CLI. Skills provide instructions; installing them does not configure credentials, grant permissions or enable execution.
Install reliquary-run-benchmarks
reliqua skills install --skill reliquary-run-benchmarks --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.6.0.
Install the customer CLI — Verified release downloads, commands and troubleshooting.
Connect MCP — Keep writes disabled for discovery and planning.
Authentication and exact scopes — Corridor names identify key configuration; the API checks its actual read and write scopes.
Follow the workflow
- Read the requested public run snapshot once. Locate its published benchmarks; preserve benchmark identity, baseline, checkpoint or optimizer coordinate, sample count and evaluation source timestamp.
- Compare only compatible reported observations. Keep missing scores unknown and retain publication or grading limitations; do not combine different harnesses or fixed sets as equivalent.
- Report absolute scores and percentage-point changes separately. A descriptive mean across benchmarks is not pooled accuracy or proof of customer model performance.
- This workflow does not order evaluations or approve benchmark publication. If comparison evidence is missing, state the gap without inferring model improvement from operational progress.
Tools and API routes
Call reliquary_connection first and use only tools registered in that connection. Route templates need the owned resource identifiers described by the existing API reference.
CLI read
reliqua runs inspect --json| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_run_monitor |
| HTTP | GET /api/monitoring/run |
Availability and authorization
A successful read does not grant execution access or establish qualified capacity. Preserve source clocks, missing values, account ownership and the limits of the returned evidence.
Back to the skills catalog — Find another workflow or connect an interface.