Inspect response-token composition
Inspect actual raw response-token volume by environment from complete trainer observations, separately from prompt counts and PPO weights.
What you get
Measured per-environment response-token counts and shares with original source time.
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
Show the actual response-token mix by environment for the latest complete observation.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-token-mix
reliqua skills install --skill reliquary-run-token-mix --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 analytics.tokenComposition from the selected public run snapshot. Use complete same-event trainer observations and preserve source timestamps and logged-step coordinates.
- Report recorded token counts and shares by environment. Preserve actual zero and missing values; never estimate token volume from prompt groups, mean response lengths or the newest checkpoint.
- Compare share changes between adjacent complete reported observations. Sampling gaps remain gaps. Do not sum sampled observations into a cumulative run total.
- These are raw response-token lengths, not PPO loss weights or verified training consumption. If tokenComposition is absent, report unavailable; promptComposition is a separate count view.
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_monitor |
| 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.