Check CPU validation readiness

Inspect owned CPU-job permission, fresh qualified workers and bounded backlog without treating permission as available capacity.

What you get

An account-specific CPU readiness diagnosis with permission and live-worker distinctions.

Requires the configured scope and current account permission; this label does not establish execution capacity.

SupportRequirement
InterfacesCLI, MCP, HTTP
Accessauthenticated read
Workflow stateavailable
Credential corridors (see workflow)resources

Ask your assistant

Example task

Can my account run a small CPU dataset validation job now?

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-readiness

reliqua skills install --skill reliquary-cpu-readiness --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

  • Use `reliqua jobs capabilities --json`, or call reliquary_jobs_capabilities after connection discovery with the resources corridor.
  • Report account permission, dataset/training submission grant, current feature gates, fresh qualified worker availability and bounded backlog separately.
  • CPU qualification covers bounded dataset_validation work only. It does not authorize GPU training, native administrator operations, worker enrollment or network rewards.
  • A configured key, allowed queue submission or an old worker observation does not prove fresh capacity. Stop at a returned refusal rather than routing around it.

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 capabilities --json
InterfaceOperation
MCPreliquary_connection
MCPreliquary_jobs_capabilities
HTTPGET /api/v1/jobs/capabilities

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.