Verify a CPU validation report
Read a frozen owned CPU report and verify its size and digest against job metadata before interpreting row/error counts.
What you get
A digest-verified frozen report interpretation with explicit dataset-validation limits.
Requires the configured scope and current account permission; this label does not establish execution capacity.
| Support | Requirement |
|---|---|
| Interfaces | CLI, MCP, HTTP |
| Access | authenticated read |
| Workflow state | available |
| Credential corridors (see workflow) | resources |
Ask your assistant
Example task
Retrieve my CPU validation report and explain which checks passed.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-cpu-report
reliqua skills install --skill reliquary-cpu-report --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.5.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 exact owned CPU job and choose an artifact ID from its frozen report metadata. CLI users run `reliqua jobs status --id JOB_ID --json` then `reliqua jobs report --id JOB_ID --artifact ARTIFACT_ID --json`, replacing placeholders with returned IDs.
- Call job_report for that exact artifact; the client verifies the report against its frozen byte size and SHA-256. A mismatch is a failed verification, not a usable report.
- Explain safe error codes, row counts and validation scope without exposing raw dataset contents. A syntactically valid dataset is not evidence of data rights, training quality, GPU execution or finalized rewards.
- Do not execute artifacts, resubmit jobs or automatically fetch unrelated report IDs.
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 jobs report --id JOB_ID --artifact ARTIFACT_ID --json| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_job_get |
| MCP | reliquary_job_report |
| HTTP | GET /api/v1/jobs/{id} |
| HTTP | GET /api/v1/jobs/{id}/artifacts/{artifactId} |
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.