Save a qualified training draft
Create a schemaVersion 2 training configuration from an exact current runtime profile and owned compatible dataset.
What you get
A saved exact-profile draft ID/revision ready for separate quoting and launch approval.
Requires current qualified profile, compatible owned dataset and resource-write authority; saving does not launch.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | gated |
| Credential corridors (see workflow) | training, resources |
Ask your assistant
Example task
Save a bounded training draft using a qualified profile and my existing dataset.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-draft
reliqua skills install --skill reliquary-training-draft --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 current training capabilities and the owned file library. Select one exact returned profile and compatible dataset; keep its full profile digest and pinned runtime fields rather than constructing a lookalike profile.
- Choose an objective, explicit maxSteps/maxHours within profile ceilings, and optional USD ceiling. A saved budget is not a quote or spending authorization.
- At the user's request, call training_draft_create with the full profile, owned datasetId and one stable caller-supplied idempotencyKey. It saves schemaVersion 2 configuration through the resources corridor; training capabilities/files use the training corridor.
- Read resource_get for the saved draft ID and revision. Saving configuration neither launches a task nor reserves credits. On unknown outcome preserve the original key; on revision conflict reload and review current state.
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_training_files |
| MCP | reliquary_training_draft_create |
| MCP | reliquary_resource_get |
| HTTP | GET /api/v1/training/capabilities |
| HTTP | GET /api/v1/training/files |
| HTTP | POST /api/resources |
| HTTP | GET /api/resources/{id} |
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.