From ucp-agentic-commerce
Authors UCP schemas for capabilities, services, payments, components, types, metas, and extensions using JSON Schema 2020-12 composition and allOf. Use when extending UCP protocols.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin ucp-agentic-commerceThis skill is limited to using the following tools:
**Fetch live spec**: Web-search `site:ucp.dev documentation schema-authoring` and fetch the page for the exact schema metadata requirements, category rules, and composition patterns.
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 spec: Web-search site:ucp.dev documentation schema-authoring and fetch the page for the exact schema metadata requirements, category rules, and composition patterns.
Also fetch https://ucp.dev/specification/reference/ for the base type schemas you'll reference.
The official 6 schema categories are:
| Category | Required Metadata | Purpose | Examples |
|---|---|---|---|
| Capability | $schema, $id, title, description, name, version | Major functional domain | checkout, order, identity_linking |
| Service | $schema, $id, title, description | Transport binding definition | REST, MCP, A2A |
| Payment Handler | $schema, $id, title, description | Payment method specification | Google Pay, Shop Pay |
| Component | $schema, $id, title, description | Reusable structural unit | payment, payment_data |
| Type | $schema, $id, title, description | Primitive data model | buyer, line_item, postal_address, total |
| Meta | $schema, $id, title, description | Schema about schemas | ucp.json, capability.json |
Note on Extensions: Extensions (e.g., fulfillment, discount, buyer_consent, ap2_mandate) are NOT a separate top-level category. They are Capabilities with an extends field that references their parent capability. An extension has the same required metadata as a Capability ($schema, $id, title, description, name, version) plus the extends field.
allOfExtensions compose with their parent capability using JSON Schema allOf:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://example.com/schemas/my-extension.json",
"title": "My Extension",
"description": "Adds X to checkout",
"name": "com.example.my_extension",
"version": "2026-01-11",
"extends": "dev.ucp.shopping.checkout",
"allOf": [
{ "$ref": "https://ucp.dev/schemas/shopping/checkout.json" },
{
"properties": {
"my_field": { "type": "object" }
}
}
]
}
dev.ucp.* — Governed by ucp.dev (official standard)com.example.* — Governed by example.com (your organization)com.shopify.* — Governed by shopify.comUse your organization's reverse-domain name for custom extensions.
schema URIallOfhttps://json-schema.org/draft/2020-12/schema)/.well-known/ucp profile with the extends field