Agent skill · forcedotcom
service-omni-sidebar-configure
Use to enable or verify the Omni-Channel sidebar on a Lightning console app. Triggers: enable the Omni sidebar, pin Omni-Channel in a console app, configure the Omni sidebar, turn on the Omni-Channel utility region, verify the pinned Omni widget. Do not use for Aura apps, standard apps, utility-bar-only Omni widgets, or to create a console app.
What it needs
About 2k tokens when loaded.
What this skill does
service-omni-sidebar-configure Enable the Omni-Channel sidebar — the pinned Omni utility region that docks to the side of a Lightning console app — by setting isOmniPinnedViewEnabled=true on that app's CustomApplication metadata and confirming the flag round-trips. This is the recommended Omni surface for console/demo orgs: reps see incoming work, presence, and the work list docked beside the record, rather than only in the collapsible utility bar. It runs once per console app and is invoked by service-omni-channel-setup-coordinate as the final rep-experience step. Inputs org-alias (required). appdevelopername (optional). The CustomApplication DeveloperName of the Lightning console app. When omitted, the skill queries AppDefinition for Lightning console apps: exactly one → adopt it; zero or many → blocked (name it explicitly). Preconditions and safety Target org authenticated via sf CLI, Service Cloud license, sf CLI ≥ 2.139.6. Omni-Channel base settings enabled (service-omni-base-settings-configure). The target must be a Lightning console app that is deployable as CustomApplication metadata. Standard apps and Aura apps are out of scope. The three-way safetowrite production guard applies. Run enable-and-report.sh resolves the target app, retrieves its CustomApplication, and reads the current isOmniPinnedViewEnabled value: already true → reused (no deploy). false or absent → sets it to true and deploys the single CustomApplication in one atomic Metadata API call, then re-retrieves to confirm the flag is true before reporting success. The deploy uses explicit --metadata "CustomApplication:<name>" (never --source-dir) and is done on its own — Metadata deploys are atomic, so the app is left unchanged on any failure. Behavior Idempotent + non-destructive. The skill only flips the single boolean; it never rewrites tabs, brand, or nav config. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-sidebar-configure