Agent skill · forcedotcom
service-itsm-agentic-setup-cmdb-bundle-deploy
Deploy (install) the CMDB Foundation base content bundle in Service Cloud ITSM against a production or sandbox org, after the CMDB feature is enabled. Use when the user asks to install the CMDB bundle, deploy CMDB Foundation, set up the CMDB base content, install CMDB out-of-the-box content, or finish CMDB setup with the base bundle. Triggers on: install CMDB bundle, deploy CMDB Foundation, CMDB base content, CMDB content bundle, bundleInstallation, finish CMDB setup. DO NOT TRIGGER when: the user wants to enable the CMDB feature for the org (that is the CMDB feature-enable skill), assign CMDB permission sets to a user (that is the CMDB access-assign skill), install optional non-base add-on bundles, deploy general (non-CMDB) metadata or packages, or work with CMDB records directly.
What it needs
About 8k tokens when loaded.
What this skill does
Deploy the CMDB Foundation Bundle (Service Cloud ITSM) Installs the CMDB Foundation (base) content bundle — the out-of-the-box configuration-item types, schema, and content that make CMDB usable. This is Layer 4, the final layer of the CMDB setup stack, and it requires the CMDB feature to already be enabled (Layer 2). Every call runs through the Salesforce-hosted Headless-360 MCP server (server key headless-360) via its four meta-tools (discover, describe, dispatchreadonly, dispatch). The org is derived from the OAuth JWT bound to the current MCP session — the skill never handles an org id, alias, or credentials — so this works identically against production and sandbox with no per-user MCP install. Scope In scope: confirming CMDB is enabled, reading the live bundle catalog, resolving the exact version of the base bundle, installing the base (CMDB Foundation) bundle, and verifying. Out of scope: enabling the CMDB feature / provisioning the CMDB tenant (Layers 0–2 — service-itsm-agentic-setup-cmdb-configure), assigning permission sets (Layer 3 — service-itsm-agentic-setup-cmdb-access-assign), installing optional add-on bundles (e.g. Component Identification Rules), CMDB record CRUD, or Discovery. This skill installs the base bundle only. Optional add-ons are intentionally out of scope. Why order matters The bundle Connect APIs (bundleListView, bundles/details, bundleInstallation) are gated by orgHasCMDBEnabled. Until the CMDB feature is enabled they return 403 FUNCTIONALITYNOTENABLED, so this skill must run after the CMDB feature-enable skill has turned the feature on. On top of the org gate, these reads also enforce the running user's own CMDB access, so a 403 FUNCTIONALITYNOTENABLED here has two distinct causes — feature-off or user-has-no-access. Step 1 disambiguates them via the feature status before sending the user anywhere; never assume a 403 means the feature is off. Mechanism All operations dispatch through headless-360 MCP tools. …
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-bundle-deploy--eea3e5