forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-command-center-configure
service-omni-command-center-configure
VerifiedUse to enable Command Center for Service V2 and configure its supported supervisor controls through the OmniChannel Settings Metadata API while preserving unrelated settings. Requires explicit apply consent, refuses production customer orgs, and verifies the seeded V2 page and tab. TRIGGER when: enable Command Center V2, configure conversation monitoring, enable agent sneak peek, enable customer sneak peek, configure whisper messaging, or enable queues and skills actions. Do not use to assign supervisor permissions or configure classic OmniSupervisorConfig metadata.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| references/api-notes.md | markdown | 2.3 KB |
| scripts/configure-and-report.shexecutable | script | 13.6 KB |
| scripts/settings_document.pyexecutable | script | 3.1 KB |
| scripts/tests/test_command_center_configure_contracts.py | script | 8.3 KB |
references/api-notes.md
View on GitHub# Command Center for Service V2 API notes
## Metadata contract
Core work item `W-24039822` and Core PR `#16874` expose these fields on `Settings:OmniChannel`:
| Metadata field | Product control |
|---|---|
| `enableCommandCenterForServiceV2` | Command Center for Service V2 |
| `enableConversationMonitoring` | Conversation monitoring |
| `enableAgentSneakPeek` | Agent sneak peek |
| `enableClientSneakPeek` | Customer sneak peek |
| `enableWhisperMessaging` | Whisper messaging |
| `enableSkillsAndQueueActions` | Queues and skills actions |
The V2 preference is Metadata API writable only when the target release contains that contract and the `OmniChannel.commandCenterForServiceV2Available` access check passes. That access check requires the feature gater and Enhanced Omni-Channel. Standard Omni orgs on the EOL extension cannot enable V2.
## ON-transition side effects
Changing `enableCommandCenterForServiceV2` from false to true invokes the existing `CommandCenterForServiceV2OrgPreference` hook. The hook:
1. inserts missing profile tab configurations for the V2 tab;
2. checks for `FlexiPage.DeveloperName='CommandCenterForServiceV2_L'`;
3. clones the platform seed only when that page is absent.
Disabling the preference does not delete the page. Re-enabling preserves an existing page. This skill enables but does not disable V2.
## Verification signals
The writer verifies the settings by a fresh Metadata API retrieve and verifies provisioning through:
```sql
SELECT Id FROM FlexiPage WHERE DeveloperName='CommandCenterForServiceV2_L'
```
using Tooling API, and:
```sql
SELECT Name FROM TabDefinition WHERE Name='standard-commandcenterforservicev2'
```
using the data API. Query errors remain `unknown` and block a successful write claim.
## User access
The org preference and its seed artifacts establish org-level readiness only. A supervisor also needs a permission set with `PermissionsCommandCenterForServiceUser=true`. This skill reports that follow-up but does not create users or permission sets.
## Whole-document requirement
Salesforce Settings metadata is deployed as a complete document. The implementation retrieves the current document and updates it in place. Do not replace this approach with a static template: a static template can silently drop existing Omni settings that are outside this skill's scope.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |