Agent skill · forcedotcom
service-omni-supervisor-config-deploy
Use to stand up a headless Omni-Channel Supervisor Configuration by deploying the classic OmniSupervisorConfig (parent plus supervisor-user and queue companions) in one atomic Metadata API deploy, idempotent via the deploy state. Requires active supervisor users, Omni base settings, and the monitored queues. Triggers: set up Omni Supervisor, configure the classic Supervisor Command Center. Do not use to create supervisor users, assign the ContactCenterSupervisor permission set, or deploy queues, service channels, or presence statuses.
What it needs
About 5k tokens when loaded.
What this skill does
service-omni-supervisor-config-deploy Deploy the classic Omni-Channel Supervisor Configuration (OmniSupervisorConfig) to a Salesforce org in a single Metadata API deploy. OmniSupervisorConfig is a full Metadata API type whose XSD embeds every companion as a repeatable child element, so the whole configuration — parent plus companions — lands atomically from one .omniSupervisorConfig-meta.xml file, and Salesforce rolls the companions back together on a partial failure. By default the deploy binds supervisors explicitly by user and lists the queues they monitor; profile scope is optional (see Behavior). Inputs bash scripts/deploy-and-report.sh <org-alias> [supervisorcount] [additionalqueuescsv] [profilescsv] [skillvisibility] [configdevelopername] org-alias (required) — must resolve via sf org display --target-org <alias>. supervisorcount (optional, default 1, range 1..5) — how many active supervisor{N}.<suffix>@example.com users to detect and bind. additionalqueuescsv (optional) — queue DeveloperNames to bind. When the coordinator supplies this list it is authoritative; when omitted, the canonical CaseQueue, messagingqueue defaults are used. Every requested queue must already exist on the org. profilescsv (optional) — opt into profile-based fallback scope; supply metadata profile fullNames (e.g. Standard,ServiceCloud). Omit it to bind supervisors by user only. skillvisibility (optional, or OMNISUPERVISORSKILLVISIBILITY) — AllSkills or AnySkill. Omitted values preserve an existing config's selection; a new config defaults to AllSkills. configdevelopername (optional, or OMNISUPERVISORCONFIGDEVELOPERNAME; default OmniSupervisor) — the exact classic OmniSupervisorConfig.DeveloperName to create or reconcile. Supply it when an org has multiple supervisor configurations; the skill never guesses between candidates. OMNISUPERVISORCONFIGMASTERLABEL optionally sets the label for a new config. Existing labels are preserved by default. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-supervisor-config-deploy--d7b5a2