From ucp-toolkit
This skill should be used when the user asks about "UCP architecture", "protocol structure", "OpenAPI spec", "OpenRPC spec", "capability design", "method naming", or needs to understand how UCP works. Provides guidance on UCP's layered architecture and spec generation.
npx claudepluginhub ibraschwan/ucp-pluginThis skill uses the workspace's default tool permissions.
Universal Commerce Protocol (UCP) is an open standard for commerce interoperability. It enables AI agents and applications to interact with e-commerce systems through a unified API specification.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.
Universal Commerce Protocol (UCP) is an open standard for commerce interoperability. It enables AI agents and applications to interact with e-commerce systems through a unified API specification.
┌─────────────────────────────────────────┐
│ Generated Specs │
│ (OpenAPI 3.1.0 + OpenRPC 1.3.2) │
├─────────────────────────────────────────┤
│ Source Schemas │
│ (JSON Schema Draft 2020-12) │
├─────────────────────────────────────────┤
│ Type Definitions │
│ (Reusable Commerce Types) │
└─────────────────────────────────────────┘
ucp/
├── source/
│ └── schemas/
│ └── shopping/ # Source JSON schemas
│ ├── checkout.json
│ ├── order.json
│ ├── payment.json
│ ├── product.json
│ ├── cart.json
│ ├── customer.json
│ ├── fulfillment.json
│ └── types/ # Reusable types
├── generated/
│ ├── openapi/ # OpenAPI 3.1.0 specs
│ │ └── shopping.openapi.json
│ ├── openrpc/ # OpenRPC 1.3.2 specs
│ │ └── shopping.openrpc.json
│ └── json-schema/ # Bundled schemas
│ └── shopping.schema.json
├── scripts/
│ ├── generate_schemas.py # Main generation script
│ ├── validate_specs.py # Validation script
│ └── generate_ts_schema_types.js
└── docs/ # Documentation
UCP methods follow dot notation: domain.capability.action
Examples:
shopping.cart.create - Create a cartshopping.cart.add_item - Add item to cartshopping.checkout.initiate - Start checkoutshopping.order.get - Get order detailsshopping.product.search - Search productsSource schemas are processed to generate:
# Generate all specs
python scripts/generate_schemas.py
# Generate TypeScript types
node scripts/generate_ts_schema_types.js
Validation ensures schema correctness:
# Validate all specs
python scripts/validate_specs.py
Validation checks:
$ref references resolveTo add a new capability:
types/ucp_request/ucp_responsevalidate_specs.pygenerate_schemas.pyCore schemas (ucp_core: true):
Capability schemas:
For detailed architecture documentation:
references/openapi-patterns.md - OpenAPI generation patternsreferences/openrpc-patterns.md - OpenRPC generation patternsexamples/full-capability-flow.md - End-to-end capability creationexamples/method-naming.md - Method naming examples