ucp

Automate UCP implementation workflows for Next.js ecommerce codebases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blenvi/blenvi --skill ucp-blenvi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ucp
Source: https://github.com/blenvi/blenvi/tree/main/.agents/skills/ucp
Command: npx skills add https://github.com/blenvi/blenvi --skill ucp-blenvi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through implementing Universal Commerce Protocol (UCP) across Next.js ecommerce projects, streamlining setup, negotiation, and scaffolded code generation.

Core Features & Use Cases

  • End-to-end guidance from init to profile and scaffold, including capability negotiation, transport selection, and roadmap generation.
  • Generates a compliant UCP workflow with discovery, plan, gaps analysis, and validation examples for REST, MCP, A2A, and embedded transports.
  • Real-world scenario: a multi-platform Next.js storefront implementing checkout, fulfillment, discounts, and identity linking with webhook support.

Quick Start

Run /ucp init to bootstrap a UCP workflow in your project.

Frequently Asked Questions about ucp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Universal Commerce Protocol in a Next.js ecommerce app?

You can implement UCP by running a guided initialization command that bootstraps a spec-grounded, config-driven workflow. It automates capability negotiation, transport selection, and code scaffolding for REST, MCP, A2A, and embedded integrations in your Next.js project.

What is UCP capability negotiation and how does it work for checkout workflows?

UCP capability negotiation is a process that clones specifications and determines supported transport protocols between platforms. It enables Next.js storefronts to dynamically discover and integrate checkout, fulfillment, and discount features across REST, MCP, or A2A endpoints.

Does this UCP scaffolding workflow support both REST and A2A transports?

Yes, the scaffolding workflow supports REST, MCP, A2A, and embedded transports. It generates compliant code and validates configurations against UCP schemas across all supported communication protocols for multi-platform Next.js ecommerce integrations.

How do I scaffold a Next.js storefront with fulfillment and webhook support?

Scaffolding a Next.js storefront with fulfillment and webhooks requires running the scaffold command after capability negotiation. It generates compliant UCP code, validates against schemas, and provides a roadmap for identity linking and webhook integration.

Can I use UCP integration for multi-platform identity linking in Next.js?

Yes, UCP integration supports multi-platform identity linking in Next.js applications. The workflow includes discovery, gap analysis, and validation examples to connect identity systems across platforms using REST, MCP, and A2A embedded transports.

What are the limitations of automating UCP schema validation in Next.js?

Automating UCP schema validation is limited to the predefined specifications cloned during initialization. It ensures compliance for configured transports like REST and A2A but requires strict adherence to the spec-grounded, config-driven process to avoid scaffolding errors in Next.js ecommerce codebases.