Check your connection

What you get

A connection diagnosis and the exact next supported discovery step.

Documented read workflow; source freshness and current service state still apply.

Ask your assistant

Example task

Check my Reliquary connection and explain what I can use next.

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

reliqua skills install --skill reliquary-connect --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 doctor --json` for the installed CLI, or call `reliquary_connection` then `reliquary_health` with an existing MCP connection. There is no HTTP equivalent of the local connection inventory; GET /api/health checks the upstream service only.
• Report the installed version, API origin, registered tools and whether a credential is configured without displaying the credential. Connection registration and health do not validate a key or establish product availability.
• Choose the next capability read for the user's task: public product readiness, owned CPU job capabilities, generation/evaluation catalog, or authenticated training capabilities. If the requested tool is absent, explain the configured connection's limit.
• Do not install a second interface when the current one supports the request. Installation requires user authorization and the reviewed release guide; do not invent a registry package.
• When the user needs help choosing a workflow, call the registered reliquary_skills tool for the installed task catalog. Catalog support states do not establish current product availability; retain the connection and live-capability distinctions.

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 doctor --json

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.