Import delivered generation data
Import one verified owned generation JSONL shard into the training library without converting formats or starting a run.
What you get
A verified delivered shard saved as an owned training-library file.
Requires delivered owned data, data rights, upload/import permission and compatible format.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | gated |
| Credential corridors (see workflow) | training, orders |
Ask your assistant
Example task
Import this delivered dataset shard into my training library after checking ownership and rights.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-training-import
reliqua skills install --skill reliquary-training-import --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
- Read training capabilities and the owned generation order. Choose a delivered JSONL file from returned delivery metadata; preserve orderId, deliveryId, fileName and whether its kind is catalogue or pinned.
- Confirm that the exact delivered content is authorized for this use and transfer. Select a compatible instruction, preference, corpus or vision format; import does not convert text/media or repair labels.
- Call training_import_delivery with the selected metadata, .jsonl library name, format and rightsConfirmed:true only after user authorization. The platform validates ownership, integrity, size and format.
- Save the returned owned library file ID. Import creates no draft or run and has no idempotency-key field; inspect the library before repeating an ambiguous import.
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_training_capabilities |
| MCP | reliquary_generation_order_get |
| MCP | reliquary_training_import_delivery |
| HTTP | GET /api/v1/training/capabilities |
| HTTP | GET /api/v1/dataset-orders/{id} |
| HTTP | POST /api/v1/training/files/from-order |
Availability and authorization
This workflow can prepare an action using existing contracts. Execution requires current server capabilities, qualified capacity, appropriate account scope, a fresh quote when applicable, and explicit approval of the concrete action. The customer preview CLI has no execution commands; MCP writes stay disabled by default.
Back to the skills catalog — Find another workflow or connect an interface.