Check product readiness
Read current product catalogs and readiness gates before choosing a supported workflow.
What you get
A product-by-product readiness explanation grounded in returned gates.
Documented read workflow; source freshness and current service state still apply.
| Support | Requirement |
|---|---|
| Interfaces | CLI, MCP, HTTP |
| Access | public read |
| Workflow state | available |
| Credential corridors (see workflow) | None |
Ask your assistant
Example task
Which Reliquary products are currently available, gated or only observable?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-product-readiness
reliqua skills install --skill reliquary-product-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 capabilities --json` for combined public readiness, generation, evaluation and compute gates. With MCP, discover the connection and read only the product catalogs needed for the request.
- Distinguish service health, database readiness, ordering permission, runtime qualification and fresh capacity. An example catalog entry is not executable capacity.
- Preserve unavailable, paused, disabled and unqualified states. Explain the specific returned gate without proposing a bypass or treating a published checkpoint as a customer service.
- Public capabilities do not validate an account key. Direct account-specific training questions to training_capabilities; owned CPU questions to jobs_capabilities.
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 capabilities --json| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_readiness |
| MCP | reliquary_catalog |
| MCP | reliquary_generation_catalog |
| MCP | reliquary_evaluation_catalog |
| MCP | reliquary_compute_catalog |
| HTTP | GET /api/ready |
| HTTP | GET /api/catalog |
| HTTP | GET /api/v1/generation/catalog |
| HTTP | GET /api/v1/evaluations/catalog |
| HTTP | GET /api/compute/catalog |
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.