菜单
Manage sequencer sync, outbox, and conflict resolution. Use when running `stateset-sync` or checking sync status, push, or pull.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manage supplier bills, payments, and AP aging. Use when recording supplier invoices, processing payments, running payment batches, or reviewing AP aging reports.
Manage customer receivables, collections, credit memos, and AR aging. Use when tracking overdue invoices, sending dunning letters, creating write-offs, or generating customer statements.
Run commerce analytics, metrics, and forecasts. Use when running `stateset-analytics` or requesting sales, customer, inventory, or demand insights and trend analysis.
Operate the StateSet autonomous engine (jobs, workflows, policies, approvals). Use when starting/stopping `stateset-autonomous`, inspecting scheduler state, or running autonomous MCP tools.
Runbook for operating the StateSet autonomous engine. Use when troubleshooting incident response, stuck jobs, approval backlogs, or autonomous operations with `stateset-autonomous`.
Manage backorders for out-of-stock items. Use when tracking unfulfilled demand, allocating incoming inventory to backorders, or prioritizing backorder fulfillment.
| name | commerce-sync |
| description | Manage sequencer sync, outbox, and conflict resolution. Use when running `stateset-sync` or checking sync status, push, or pull. |
Synchronize local events with the sequencer using VES.
sync_status after each cycle.stateset-sync status, stateset-sync push, stateset-sync pull, stateset-sync resolve.bash /mnt/skills/user/commerce-sync/scripts/sync-status.sh, bash /mnt/skills/user/commerce-sync/scripts/sync-push.sh, bash /mnt/skills/user/commerce-sync/scripts/sync-pull.sh.sync_status, sync_push, sync_pull, sync_outbox, sync_conflicts, sync_resolve.sync_status, sync_outbox, sync_conflicts — no --apply needed.sync_push, sync_pull, sync_resolve — requires --apply.stateset-sync status
stateset-sync push --apply
stateset-sync pull --apply
stateset-sync resolve --strategy ours --conflict conflict_12 --apply
{"status":"synced","pending":0,"conflicts":0,"last_push":"2026-03-25T09:45:00Z","events_pushed":12}
stateset-sync init to generate .sync.json.stateset-sync register.ours, theirs, manual) before retrying.pending count not decreasing: check network connectivity and sequencer health with sync_status.SYNC_CONFIG_MISSING: No .sync.json found; run stateset-sync init to generate the config.SYNC_SIGNATURE_INVALID: Event signature verification failed; re-register keys with the sequencer.SYNC_CONFLICT_UNRESOLVED: One or more conflicts must be resolved before the sync cycle can complete.