/service-catalog-template-coordinate

name: service-catalog-template-coordinate
description: "Single entry point for the Unified Catalog Service Process lifecycle in Salesforce — find and deploy Service Process templates, create a Service Process from scratch, activate one, or organize it under a catalog category. It discovers the platform's own guided setup recipe for the requested operation and follows its live steps, so results and safeguards always match the org. Use when a business user wants to work with Unified Catalog or Service Process templates, find or browse templates, deploy or install a named template, set one up end to end, activate a Service Process, or add, file, or place a Service Process under a catalog or category. Triggers on: set up Unified Catalog templates, find a Service Process template, deploy the X template, activate a service process, add a service process to a catalog. DO NOT TRIGGER when the request concerns Data Cloud data kits, CRM Analytics, or App Framework catalogs rather than Unified Catalog Service Processes."
metadata:
  version: "2.0"
  domains: ["Service"]
  minApiVersion: "67.0"
  # This skill now performs the Unified Catalog Service Process operations itself by following the
  # platform's guided setup recipes, so it declares the Unified Catalog access gate (it no longer
  # merely delegates to child skills that owned the gate).
  accessCheck:
    - type: "accessCheck"
      value: "IndustriesEpc.orgHasUnifiedCatalog"
  mcpTools:
    headless-360:
      tools: ["describe", "discover", "dispatch", "dispatch_readonly"]
      semver: ">=1.0.0"
allowed-tools: Read AskUserQuestion mcp__headless-360__describe mcp__headless-360__discover mcp__headless-360__dispatch mcp__headless-360__dispatch_readonly

Unified Catalog Service Process Coordinator

The single entry point for the Unified Catalog **Service Process** lifecycle: **find** a template, **deploy** one, **create** a Service Process from scratch, **activate** it, and **organize** it under a catalog category. Rather than hard-coding each operation's API steps, this skill **discovers the platform's own guided setup recipe** for the requested operation, reads that recipe's live steps, and follows them. The recipe is the source of truth — so the exact steps, ordering, and safeguards always match what the org actually enforces, and never drift from a frozen copy.

The connected org is fixed for the session — this skill takes no org alias and handles no credentials.

Scope

• **In scope**: Finding / browsing / ranking Service Process templates; deploying a named template;

creating a Service Process from scratch; activating a Service Process; placing a Service Process under a catalog category; and running the guided end-to-end flow (find → deploy → activate). Each operation is carried out by discovering and following the platform's guided recipe for it.

• **Out of scope**: Authoring or editing template content; enabling the Unified Catalog feature or other

ITSM setup (a separate `service-itsm-*-configure` concern — this skill self-heals a **per-user** access gap but does not turn the feature on for an org that lacks the license); bulk operations; Data Cloud data kits, CRM Analytics, or App Framework catalogs.

---

How this skill works — discover, read, follow

Every operation runs through the **headless-360** setup server, which exposes the org's guided setup recipes and the operations behind them. The loop is always the same:

1. **Discover** the recipe for the user's operation with a plain-language query (e.g. *"deploy a Unified Catalog service process from a template"*). Take the top-ranked recipe. 2. **Describe** that recipe to read its **ordered steps**, **preconditions**, and the operation behind each step (a ready-to-call `METHOD path`). 3. **Follow** the steps in order — read-only lookups first, writes only when the recipe says so — and **verify** with the recipe's own verify step before reporting success.

Do **not** invent or freeze a step sequence. If discover returns nothing for a live route, that does not mean the route is missing (standard `/query` and `/sobjects` routes are not always indexed) — follow the recipe's guidance. The shared mechanics — full call shapes, the response envelope, the per-user access self-heal, and the SOQL-escaping rule — live in `references/mcp-invocation.md`; the per-operation recipe catalog (find / deploy / create / activate / place), each recipe's ordered steps, and every load-bearing gotcha live in `references/operations.md`. **Read both before running any operation.**

Operations and the recipe each one follows

| Operation | Discover with (plain-language intent) | The recipe you follow | |-----------|---------------------------------------|-----------------------| | **Find / browse templates** | "list Unified Catalog service process templates" | The from-template recipe's **list** step (there is no separate search recipe) — rank the returned templates against the stated need | | **Deploy a named template** | "deploy a Unified Catalog service process from a template" | The **from-template** recipe: list → (collect any required flow inputs) → deploy → verify | | **Create from scratch** | "create a Unified Catalog service process from scratch" | The **from-scratch** recipe: create → persist the anchor → attach required fields → (optional) place → verify | | **Activate a Service Process** | "activate a Unified Catalog service process" | The **activate** recipe: an **ordered precondition chain** (intake active → agent action active → then the process) | | **Place under a catalog category** | "place a service process under a catalog category" | The from-scratch recipe's **place-under-category** step (a join record, not a field) | | **Guided end-to-end** | discover per stage, in order | from-template (deploy) → then activate — chain the recipes |

---

Access (Phase 0) — per-user, self-healing

Unified Catalog access is **per-user**. Do not pre-check with a