order.update

Update existing orders via confirmed patches with rollback on partial failures.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill order-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: order.update
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/skills/order.update
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill order-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables updating existing orders by applying a controlled patch after obtaining explicit user confirmation. It ensures traceability via operation_id and keeps systems (Trello and Sheets) consistent, with rollback on partial failures.

Core Features & Use Cases

  • Controlled patches: apply only allowed fields.
  • Explicit confirmation: requires summary + confirm or cancel before mutation.
  • End-to-end traceability: uses operation_id_ref for audit and rollback support. Use case: Update an order's quantity or date by referencing folio or operation_id_ref.

Quick Start

Provide the order reference and a patch detailing the changes, then confirm the action to apply updates.

Frequently Asked Questions about order.update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely patch an existing order with an explicit confirmation flow?

Updating order quantity or date requires providing a folio or operation_id_ref and a patch describing the changes. The system enforces input validation and requires explicit confirmation before applying the controlled patch to the order.

What is operation_id_ref used for when updating orders?

The operation_id_ref ensures end-to-end traceability and maintains idempotency during order updates. It enables audit tracking and supports rollback capabilities if a partial failure occurs across connected systems.

Can I use order references to update shipping details and notes across Trello and Sheets?

Yes, you can update shipping details and notes by providing a folio or operation_id_ref with your patch. The system maintains cross-system consistency between Trello and Sheets, utilizing rollback capabilities to handle partial failures.

What happens if an order update partially fails across integrated workflows?

If an order update partially fails across integrated workflows, the system executes a rollback to ensure cross-system consistency. The operation_id maintains idempotency, preventing duplicate or inconsistent states during the patch application.

What is the best way to ensure idempotency when applying patches to existing orders?

The best way to ensure idempotency when applying patches to existing orders is by utilizing an operation_id. This enforces input validation, maintains traceability, and ensures that repeated patch applications do not cause duplicate mutations.