From acp-agentic-commerce
Implements ACP capability negotiation for dynamic discovery of shared capabilities, extensions, payment handlers, and interventions between agents and merchants.
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:
site:github.com agentic-commerce-protocol rfcs capability_negotiation for the capability negotiation RFChttps://developers.openai.com/commerce/specs/checkout/ for how capabilities appear in checkout requests/responsessite:github.com agentic-commerce-protocol spec json-schema capabilities for the capabilities JSON schemaACP agents and merchants may support different features. Capability negotiation allows them to dynamically discover what they both support, so the session uses only mutually available features.
create request, the agent includes a capabilities object listing what it supportsThe capabilities object contains:
capabilities — Major features (checkout, orders, etc.)extensions[] — Optional add-ons (discount, intent traces, affiliate attribution)payment_handlers[] — Supported payment methodsinterventions — Structured object with sub-fields: supported, required, enforcement, display_context, redirect_context, max_redirects, max_interaction_depthExtensions declare a parent capability via extends. If the parent capability is not in the negotiated intersection, the extension is automatically pruned — no extra logic needed.
Interventions are actions that require human involvement. They are represented as a structured object (not a flat array) with sub-fields including supported, required, enforcement, display_context, redirect_context, max_redirects, and max_interaction_depth.
Intervention types include:
The agent advertises which interventions it can handle. If the merchant requires an intervention the agent can't handle, the checkout may not proceed.
discount@2026-01-27)Fetch the capability negotiation RFC for the exact capabilities object schema, extension pruning rules, and negotiation semantics before implementing.