Inspect live RL progress
Read stored public trainer and controller observations, keeping checkpoint progress, collection freshness and missing data distinct.
What you get
A source-dated progress report with actual coordinates, freshness and unresolved gaps.
Documented public read workflow; stored availability, source freshness and metric qualification still apply.
| Support | Requirement |
|---|---|
| Interfaces | CLI, MCP, HTTP |
| Access | public read |
| Workflow state | available |
| Credential corridors (see workflow) | None |
Ask your assistant
Example task
Is the current RL run progressing, and which observations are fresh?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-run-monitor
reliqua skills install --skill reliquary-run-monitor --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.6.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 selected public run once through `reliqua runs inspect --json` or reliquary_run_monitor. Select another published run only when requested.
- Inspect mode, availability, sources, source timestamps and collection times before interpreting progress. Report unavailable, stale and missing fields explicitly; a fresh collection is not a new optimizer step.
- Keep trainer logged step, batch policy checkpoint, optimizer coordinate, controller leases, publication and held-out evaluation separate. Explain only the progress established by returned observations.
- Do not restart, pause, cancel, redeploy or change the trainer, collector or miners. This workflow reads public stored telemetry and grants no operator authority.
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 runs inspect --json| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_run_catalog |
| MCP | reliquary_run_monitor |
| HTTP | GET /api/monitoring/runs |
| HTTP | GET /api/monitoring/run |
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.