forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-command-center-analyze
service-omni-command-center-analyze
VerifiedUse to analyze whether an org should use Command Center for Service V2 or classic Omni Supervisor and recommend the next action without making changes. Triggers: detect Command Center V2 versus classic, check supervisor readiness, choose a supervisor experience, diagnose Command Center availability, assess Omni Supervisor setup. Do not use to enable V2, assign permissions, or deploy configuration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| references/api-notes.md | markdown | 3.2 KB |
| scripts/analyze.shexecutable | script | 8.9 KB |
| scripts/tests/_bootstrap.py | script | 4.3 KB |
| scripts/tests/test_command_center_analyze_contracts.pyexecutable | script | 6.5 KB |
references/api-notes.md
View on GitHub# API notes — service-omni-command-center-analyze
## The three-dimensional V2 gate
Command Center for Service V2 renders only when **all** of the following hold, per the runtime
access check on the seeded page (`OmniChannel.userCanUseCommandCenterForServiceV2`):
```text
orgHasCommandCenterForServiceV2Enabled
= release Gater
AND CommandCenterForServiceV2 org preference
AND NOT StandardOmniEOLExtension
AND UserPermissions.CommandCenterForServiceUser (per user)
```
A single boolean cannot capture this, so the detector reports an explicit **state** across the
capability, preference/seed, and per-user permission dimensions.
## Why the preference is read via a proxy
The `CommandCenterForServiceV2` org preference is flipped only by an **internal** Setup
`SettingMutator` (`OmniChannelSettings.OrgPreferences.commandCenterForServiceV2`) and is **not**
exposed by the v66 Metadata API `OmniChannelSettings` (nor any other proven public write/read
surface). Its ON-flip, however, has an observable side effect: the platform seeds the
`CommandCenterForServiceV2_L` FlexiPage into a DB row and registers the V2 tab (idempotently). The
detector therefore treats the **seeded FlexiPage** as the proxy for "preference is ON":
- capability present + seed present ⇒ preference was enabled.
- capability present + seed absent ⇒ preference is off (`v2_available_not_enabled`).
This proxy is called out in the output; the detector does not claim to read the preference directly.
## Signals and queries
| Signal | Query | Notes |
|---|---|---|
| V2 capability | `SELECT Id FROM PermissionSet WHERE PermissionsCommandCenterForServiceUser = true LIMIT 1` | A `No such column`/`INVALID_FIELD` error ⇒ capability **absent** (org schema has no such user permission). Success ⇒ capability present. Any other error ⇒ `unknown` ⇒ `ambiguous`. |
| Seeded FlexiPage | Tooling: `SELECT Id FROM FlexiPage WHERE DeveloperName='CommandCenterForServiceV2_L'` | Presence ⇒ preference enabled + page seeded. Query error ⇒ `unknown` ⇒ `ambiguous`. |
| V2 tab | `SELECT Name FROM TabDefinition WHERE Name='standard-commandcenterforservicev2'` | Best-effort cross-check. Error ⇒ `"unknown"`; state falls back to capability + seed. |
| Supervisor permission | `SELECT Id FROM PermissionSetAssignment WHERE AssigneeId='…' AND PermissionSet.PermissionsCommandCenterForServiceUser = true` | Catches both permission-set and profile-granted permission (profiles surface as owned permission sets). Only run when a supervisor is supplied. |
| Legacy config | Tooling: `SELECT Id FROM OmniSupervisorConfig` | Informational count for the classic path. |
## Seed/tab consistency
The enable hook performs **two** side effects — tab registration and FlexiPage seed. A partial
failure can leave exactly one present. When both signals are known and disagree, the detector
returns `v2_seed_incomplete` (re-provision or apply the manual Setup step) rather than a misleading
`v2_ready`.
## Why `ambiguous` blocks
The review's rule is explicit: when a required signal cannot be read through a supported API, **block
and do not guess**. `ambiguous` is the only state that exits non-zero, so a coordinator will not
proceed to enable or configure on unproven state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |