commerce-sync

Name: commerce-sync
Availability: InStock
Author: StateSet

Synchronize local events with the sequencer using the VES-based workflow.

Updated Jan 19, 2026

Search Tags:#automation #cli #sync #conflicts #outbox #sequencer #ves

Ready to run

npx skills add https://github.com/stateset/icommerce-skills --skill commerce-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commerce-sync
Source: https://github.com/stateset/icommerce-skills/tree/main/skills/commerce-sync
Command: npx skills add https://github.com/stateset/icommerce-skills --skill commerce-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinating distributed iCommerce event data between a local store and the central sequencer can be error-prone and requires careful handling of outbox mutations and conflicting updates.

Core Features & Use Cases

Initialize sync with local keys and configuration to establish trusted communication with the sequencer.
Push local outbox events to the sequencer and pull remote events to keep the local store up to date.
Resolve conflicts and reconcile divergent histories to maintain eventual consistency in multi-system deployments.
Use Case: A deployment with multiple services emitting events can stay synchronized by running stateset-sync push and pull in a scheduled workflow.

Quick Start

Initialize the sync config, then push and pull to begin synchronization with the central sequencer.

Frequently Asked Questions about commerce-sync

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

FAQPage Schema

How do I synchronize local events with a central sequencer?▼

You can synchronize local events by initializing the local sync config with cryptographic keys, then using CLI commands to push outbox events and pull remote changes from the sequencer.

What is the VES-based workflow for resolving event conflicts?▼

The VES-based workflow resolves conflicts by reconciling divergent histories during synchronization, ensuring eventual consistency across multi-system deployments when pulling remote event changes.

How do I push local outbox events to the sequencer?▼

Pushing local outbox events to the sequencer requires the stateset-sync tooling and local sync configuration to execute push operations via standard CLI usage or MCP tools.

Do I need cryptographic keys to coordinate local events with the sequencer?▼

Yes, cryptographic keys are required to initialize the sync config and establish trusted communication with the central sequencer for performing push, pull, and resolve operations.

Can I automate event synchronization across multiple services?▼

Yes, you can automate event synchronization across multiple services by running stateset-sync push and pull operations within a scheduled workflow to maintain eventual consistency.

What are the limitations of synchronizing distributed iCommerce event data?▼

Synchronizing distributed iCommerce event data requires careful handling of outbox mutations and conflicting updates; without proper conflict resolution, divergent histories may cause inconsistency across systems.