Agent skill · forcedotcom
service-itsm-agentic-setup-cmdb-coordinate
Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org. Use when the user asks to set up CMDB, enable Configuration Management Database, configure the ITSM CMDB, onboard CMDB from scratch, wants a guided walkthrough of CMDB enablement, or asks what CMDB setup steps are available. Triggers on: set up CMDB, enable CMDB, configure CMDB, CMDB onboarding, Configuration Management Database setup, ITSM CMDB walkthrough. DO NOT TRIGGER when: the user asks about a specific CMDB sub-step directly (e.g. only installing a bundle, only assigning permission sets), CMDB record CRUD (creating CIs, relationships), Discovery/Service Graph Connector configuration, or general ITSM queries without CMDB setup intent.
What it needs
About 6k tokens when loaded.
What this skill does
CMDB Setup Orchestrator (Service Cloud ITSM) Guide the user through enabling the Configuration Management Database (CMDB) in Service Cloud ITSM by presenting the ordered setup layers, delegating each to a specialized child skill, and tracking progress until CMDB is usable end-to-end. Each child skill runs through the Salesforce-hosted Headless-360 MCP server, so the same flow works against production and sandbox — the org is bound to the current MCP session, with no per-user MCP install. Goal Act as the top-level coordinator for CMDB enablement. Present the user with the ordered layers, invoke the appropriate child skill for each, verify the layer succeeded before moving on, and after each layer completes return to the menu with updated progress until CMDB is ready or the user stops. The CMDB prerequisite stack (why order matters) CMDB is gated by a 4-layer stack. Every CMDB Connect API checks orgHasCMDBEnabled, which is orgHasCMDBPermission && OrgPreferences.CMDBEnabled. Failing the gate returns 403 FUNCTIONALITYNOTENABLED. The layers must be satisfied in order: Layer 0 is a hard prerequisite: if the org was not born with the CMDB SKU, no API can grant it and setup cannot proceed. The orchestrator surfaces this clearly and stops. Behavior 1. Extract context from conversation Before presenting options, scan chat history for: The target org (alias/username) — required by every child skill Which layers are already done (skip or mark as done) Any constraints the user mentioned (e.g. "just enable it, we'll assign users later") Derive layer status from the most recent layer activity in the transcript. On a long or resumed conversation (e.g. a headless session continued later), do not treat an earlier-highlighted layer as still current — re-derive which layer is active from the latest child-skill result, and if it is ambiguous, re-confirm with the user before re-presenting the menu. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-itsm-agentic-setup-cmdb-coordinate--567fa4