Ucp services vertical

Skill ViryaZheng/ucp-onboard/skills/ucp-services-vertical

Designs draft UCP vendor-namespace extensions for service commerce, including service capability profiles, scope, pricing, deliverables, acceptance, and settlement lifecycle. Use when the user wants to model non-product services such as consulting, design, AI-agent labor, or SaaS on-demand transactions.From its SKILL.md

Install

npx -y skills add ViryaZheng/ucp-onboard --skill ucp-services-vertical

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, 216 tokens by cl100k_base, as published. Nobody here has run it

UCP Services Vertical

Use this skill to keep services work separate from shopping onboarding.

Output

Create a draft package under store/clients/{client_name}/services-vertical/:

service-profile.json
service-catalog.json
lifecycle.md
vendor-namespace.md

Workflow

Define the vendor namespace, such as com.example.services.
Model service offerings with scope, deliverables, pricing, and acceptance.
Define lifecycle states: booked, in_progress, delivered, verified, settled, canceled.
Keep payment authorization separate from service acceptance.
Document what would need to graduate from vendor namespace to core UCP.

Read references/services-model.md for the draft object model.

Hard Rules

Do not mix service capabilities into dev.ucp.shopping.*.
Do not promise official UCP support for services.
Keep this as vendor-namespace design until the standard accepts a services vertical.

What ships with it: 1 file

771 B alongside SKILL.md

references/

services-model.md771 B