Agent skill · forcedotcom
service-omni-command-center-analyze
Use 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.
What it needs
About 3k tokens when loaded.
What this skill does
service-omni-command-center-analyze Decide, without changing anything, which supervisor experience an org should use and what to do next. Command Center for Service V2 is gated on three independent dimensions — org capability (release gater), the CommandCenterForServiceV2 org preference (whose ON-flip seeds the CommandCenterForServiceV2L FlexiPage and registers the V2 tab), and the per-supervisor CommandCenterForServiceUser permission. A single boolean cannot express that, so this skill returns an explicit state plus the recommended follow-up skill (e.g. service-omni-supervisor-config-deploy for the classic path). It is the entry point of the Command Center flow — service-omni-channel-setup-coordinate runs it first — and is safe to run on any org, including production, because it only reads. Inputs org-alias (required). supervisorusernameorid (optional). A Username (…@…) or 15/18-char User Id (005…). When given, the per-user CommandCenterForServiceUser permission is evaluated; when omitted, the permission dimension is reported as not-checked and readiness is org-level only. Preconditions and safety Target org authenticated via sf CLI, Service Cloud license, sf CLI ≥ 2.139.6. Read-only — no safetowrite guard is needed; the skill issues only SOQL/Tooling queries. Run analyze.sh gathers observable signals and maps them to a state: Signal Source Meaning --- --- --- V2 capability SELECT Id FROM PermissionSet WHERE PermissionsCommandCenterForServiceUser = true probe If the user-permission column does not exist on the org schema, V2 is not available. Seeded FlexiPage Tooling: FlexiPage where DeveloperName='CommandCenterForServiceV2L' Present ⇒ the org preference was enabled and the page was seeded. V2 tab TabDefinition (best-effort) Cross-checks the seed; a seed/tab mismatch indicates a partial provision. Supervisor permission PermissionSetAssignment joined on PermissionSet.PermissionsCommandCenterForServiceUser Whether the named supervisor can use V2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-command-center-analyze--b32388