From acp-agentic-commerce
Implements ACP fulfillment options: shipping, digital delivery, in-store pickup, local delivery. Covers selection, rate calculation, delivery windows, tracking, and order updates per OpenAI commerce specs.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin acp-agentic-commerceThis skill is limited to using the following tools:
**Fetch live docs**:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Fetch live docs:
https://developers.openai.com/commerce/specs/checkout/ — fulfillment options are part of the checkout specsite:github.com agentic-commerce-protocol spec json-schema FulfillmentOption for the schemasite:github.com agentic-commerce-protocol rfcs orders fulfillment for fulfillment in orders| Type | Use Case | Key Fields |
|---|---|---|
| shipping | Physical delivery to address | Carrier, tracking number/URL, delivery windows |
| digital | Downloads, licenses, access | Access URL, license key, expiration date |
| pickup | In-store or locker collection | Location, ready-by window, pickup-by deadline |
| local_delivery | Same-day/local service delivery | Service area, delivery window |
fulfillment_options[] based on items and addressfulfillment_option_idfulfillment_option_id in an updateEach option includes:
id — Unique identifier for this optiontype — One of the four types abovetitle — Display name (e.g., "Standard Shipping")subtitle — Additional info (e.g., "5-7 business days")carrier — Carrier name for shippingTime-based constraints:
After checkout completion, fulfillment details appear in order webhook events:
Fetch the checkout spec and JSON schema for exact FulfillmentOption field names, types, and required fields before implementing.