Manage saved resource drafts
Inspect and edit owned saved resource configurations with exact revision control and no implied execution.
What you get
An inspected or saved owned draft with exact revision and no implicit launch.
Mutations require user intent, scoped write authority and exact revision; archive requires explicit approval.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | gated |
| Credential corridors (see workflow) | resources |
Ask your assistant
Example task
Find my saved draft and update its reviewed configuration without launching it.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-resource-drafts
reliqua skills install --skill reliquary-resource-drafts --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
- List owned resources with supported kind, archived and cursor filters only as needed. Read resource_get for the exact ID and current revision before editing or archiving.
- For a requested new draft use resource_create with supported kind, reviewed name/config and a stable caller-supplied idempotencyKey. Configuration must fit the registered schema and platform validation; training drafts should use exact-profile training_draft_create instead.
- For a requested replacement use resource_update with current revision, kind, name and full config. HTTP carries X-Resource-Revision; a conflict requires reloading and review rather than overwriting another edit.
- For archive, obtain explicit approval of that exact draft and call resource_archive with current revision and approveExecution:true. Archive does not cancel a running task.
- Saving/editing a draft does not launch or reserve execution. Preserve the original create key after an unknown result; update/archive have no key field and require current-state inspection before any repeat.
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_resources_list |
| MCP | reliquary_resource_get |
| MCP | reliquary_resource_create |
| MCP | reliquary_resource_update |
| MCP | reliquary_resource_archive |
| HTTP | GET /api/resources |
| HTTP | GET /api/resources/{id} |
| HTTP | POST /api/resources |
| HTTP | PATCH /api/resources/{id} |
| HTTP | DELETE /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.