Stats
Actions
Tags
From acp-agentic-commerce
Implements ACP intent traces for cart abandonment signals with 10 reason codes. Enables analytics, recovery workflows, and conversion optimization in agentic commerce checkouts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/acp-agentic-commerce:acp-intent-tracesThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fetch live docs**:
Fetch live docs:
site:github.com agentic-commerce-protocol rfcs intent_traces for the intent traces RFChttps://developers.openai.com/commerce/specs/checkout/ for how intent traces integrate with checkoutsite:github.com agentic-commerce-protocol spec json-schema intent for the schemaIntent traces are a built-in ACP extension that provides structured cart abandonment signals. When a buyer abandons a checkout, the agent sends a trace explaining why — enabling merchants to understand conversion barriers and automate recovery.
| Code | Meaning |
|---|---|
price_sensitivity | Total was too expensive |
shipping_cost | Shipping cost was a barrier |
shipping_speed | Delivery time was too slow |
product_fit | Product didn't match buyer's needs |
trust_security | Buyer didn't trust the merchant/payment |
returns_policy | Return/refund policy was inadequate |
payment_options | Preferred payment method unavailable |
comparison | Buyer is comparison shopping |
timing_deferred | Buyer wants to purchase later |
other | Doesn't fit other categories |
POST /checkout_sessions/{id}/cancel, including a single reason_code (required enum string, exactly one per trace)Like all extensions, intent traces must be negotiated:
intent_traces in capabilities.extensions[]trace_summary — Optional free-text summary of the abandonment reason (max 500 characters)metadata — Optional flat key-value map for additional context (string keys and string values only)Intent traces are write-only — they are sent on the POST /checkout_sessions/{id}/cancel endpoint and are never echoed back in GET responses. This prevents information leakage and ensures traces are used only for analytics and recovery workflows.
other is better than no signalreason_code (required enum string); if the buyer has multiple reasons, choose the most significant oneFetch the intent traces RFC for exact trace payload structure, reason code definitions, and integration points before implementing.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin acp-agentic-commerceDiagnose and fix checkout abandonment — audit checkout flow for friction points, score abandonment risk, rank top friction sources by impact, and output specific copy/UX fixes using RMBC principles.
Implements ACP REST checkout API: create, update, retrieve, complete, cancel sessions with state machine, data models, and headers. For merchant endpoints and AI agent flows.
Implements AP2 Intent Mandate for pre-authorizing autonomous agent purchases using user-signed constraints, expiry, merchants, SKUs, and Python-typed schema.