Check observation freshness
Inspect collection health and the published monitoring snapshot to explain missing or stale observations.
What you get
A freshness and coverage diagnosis without changing collection services.
Documented read workflow; source freshness and current service state still apply.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | public read |
| Workflow state | available |
| Credential corridors (see workflow) | None |
Ask your assistant
Example task
Is Reliquary monitoring fresh, and which observations are missing?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-monitoring-health
reliqua skills install --skill reliquary-monitoring-health --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
- After connection discovery call reliquary_monitoring_health. Read reliquary_monitoring_snapshot only when its published observations help explain the collection status.
- Keep response time, collection time and source time separate. Report unavailable sources, partial collection and stale observations explicitly; missing data is not zero.
- Summarize public service observation only. Collection health does not prove successful customer execution, network rewards or available training capacity.
- Do not inspect private operations, change collectors or schedule polling as part of this read.
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.
| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_monitoring_health |
| MCP | reliquary_monitoring_snapshot |
| HTTP | GET /api/monitoring/health |
| HTTP | GET /api/monitoring/snapshot |
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.