Inspect published analytics

Read one supported public analytics view with bounded filters and source-specific metric meanings.

What you get

A focused interpretation of one published analytics view with units and provenance.

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

SupportRequirement
InterfacesMCP, HTTP
Accesspublic read
Workflow stateavailable
Credential corridors (see workflow)None

Ask your assistant

Example task

Explain the published training analytics and what they actually measure.

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-network-analytics

reliqua skills install --skill reliquary-network-analytics --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

  • Choose one view supported by the registered reliquary_monitoring_analytics schema, such as network, generation, training, sft or evaluations. Use only fields allowed by that schema, not guessed dashboard parameters.
  • Start with broad published evidence and add a task/run filter only when the user supplied or the response published its identifier. Keep user-owned customer tasks separate from public network views.
  • Use documented units and source clocks. An accepted or audited count does not establish model quality or finalized reward payment. Report stale, missing and incomplete counts.
  • Return the relevant result and its provenance; do not expose unrelated operational identifiers or private data.

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.

InterfaceOperation
MCPreliquary_connection
MCPreliquary_monitoring_analytics
HTTPGET /api/monitoring/analytics/{view}

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.