メニュー
Handle customer service operations for iCommerce. Use when managing tickets, order issues, returns, refunds, or support playbooks.
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-customer-service |
| description | Handle customer service operations for iCommerce. Use when managing tickets, order issues, returns, refunds, or support playbooks. |
Coordinate cross-domain customer support workflows.
stateset in natural language with --apply for writes.--apply needed.returns create, refund issue, ticket updates — requires --apply.stateset "look up order ORD-123 for customer cust_456"
stateset returns create --order ORD-123 --reason "wrong size" --apply
stateset refund issue --order ORD-123 --amount 49.99 --apply
stateset tickets list --status open --customer cust_456
{"status":"resolved","customer_id":"cust_123","order_id":"ord_123","resolution_code":"refund_issued","agent":"auto","elapsed_ms":1240}
resolution_code empty: ensure the playbook maps the issue type to a code in customer-service-playbooks.md.--timeout 30000; check stateset daemon health via stateset status.CS_MISSING_IDENTIFIER: Customer email, order number, or cart ID is required to proceed.CS_RESOLUTION_UNMAPPED: The issue type has no mapped resolution code in the playbook.CS_TICKET_CONFLICT: Ticket status conflicts with the requested action; verify current state.