Skip to content

forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-supervisor-surface-deploy

service-omni-supervisor-surface-deploy

Verified

Use to populate the Omni-Channel Supervisor action + tab surface on an existing OmniSupervisorConfig by inserting the standard OmniSupervisorConfigAction and OmniSupervisorConfigTab companion rows via the Data API, idempotent (inserts only the missing types). Requires an OmniSupervisorConfig from service-omni-supervisor-config-deploy. Triggers: give the supervisor the standard action buttons and tabs, add Wallboard/Agents/Queues tabs to Omni Supervisor, configure supervisor actions like Change Queues/Skills. Do not use to create the supervisor configuration itself, create supervisor users, assign the supervisor permission set, or add custom-action / FlexiPage / AWS-dashboard / AI-agent surfaces (those need an external reference and must be set up in Setup).

FileKindSize
SKILL.mdskill md5.9 KB
references/api-notes.mdmarkdown3.2 KB
scripts/deploy-and-report.shexecutablescript12.1 KB
scripts/tests/_bootstrap.pyscript4.0 KB
scripts/tests/test_supervisor_surface_contracts.pyexecutablescript6.0 KB

references/api-notes.md

View on GitHub
# Omni Supervisor surface (Action + Tab) - API notes

## What this leaf writes

Plain Data API inserts, one row per missing type:

- `OmniSupervisorConfigAction` - createable fields: `OmniSupervisorConfigId`, `OmniSupervisorActionType` (picklist), `DisplayOrder`.
- `OmniSupervisorConfigTab` - createable fields: `OmniSupervisorConfigId`, `OmniSupervisorTabType` (picklist), `DisplayOrder`.

Both are companions of `OmniSupervisorConfig`. Because they are createable child sObjects, the surface is populated without re-deploying the parent `OmniSupervisorConfig` metadata document - that document is owned by `service-omni-supervisor-config-deploy` and carries the user/queue companions. Splitting the surface into a Data API leaf keeps the two skills from fighting over the same whole-document metadata file.

## Why "reference-free types only"

Neither companion exposes a reference field in `describe` (only `OmniSupervisorConfigId`, the `*Type`, and `DisplayOrder` are createable). So a type that needs to point at something external cannot be expressed as a bare row and must be configured in Setup. This leaf blocks up front on:

- Action types matching `*.CustomAction` or `*.AWSDashboard`.
- Tab types `FlexipageType`, `AIAgents`, `AgentforceSDR`.

## OmniSupervisorActionType vocabulary (org-verified, API 66)

Reference-free (this leaf's `SAFE_ACTIONS`, and the default set):

- `AllAgents.ChangeQueues`
- `AllAgents.ChangeSkills`
- `AllAgents.ChangeGroups`
- `AllAgents.AssignLearning`
- `QueuesBacklog.ManageQueues`

Reference-required (blocked - configure in Setup): `AllAgents.CustomAction`, `AllAgents.AWSDashboard`, `AgentDetails.CustomAction`, `QueuesBacklog.CustomAction`, `QueuesBacklog.AWSDashboard`, `QueueDetails.CustomAction`, `AssignedWork.CustomAction`, `AssignedWork.AWSDashboard`, `AssignedWorkDetails.CustomAction`, `SkillsBacklog.CustomAction`, `SkillsBacklog.AWSDashboard`, `SkillDetails.CustomAction`.

## OmniSupervisorTabType vocabulary (org-verified, API 66)

Reference-free (this leaf's `SAFE_TABS`): `Wallboard`, `Agents`, `QueuesBacklog`, `AssignedWork`, `SkillsBacklog`, `Reports`, `Alerts`. The default set is the first five (the core supervisor panels); `Reports` and `Alerts` are accepted when requested explicitly.

Reference-required (blocked - configure in Setup): `FlexipageType`, `AIAgents`, `AgentforceSDR`.

## Idempotency and ordering

The requested types are diffed against the rows already on the config (`SELECT OmniSupervisorActionType/OmniSupervisorTabType ... WHERE OmniSupervisorConfigId = :id`). Existing types are reported `reused`; missing types are inserted. New `DisplayOrder` values start one above the current maximum for that companion, so ordering already configured in Setup is preserved and re-runs make no writes.

`DisplayOrder` is not required to be unique across rows; appending after the maximum simply keeps newly added items at the end of the supervisor's list.

## Related

- `service-omni-supervisor-config-deploy` - creates the parent `OmniSupervisorConfig` and its user/queue companions (prerequisite).
- `service-omni-supervisor-permset-assign` - grants supervisors the `ContactCenterSupervisor` permission set.
- `service-omni-command-center-analyze` - reports whether the org is on the classic supervisor surface vs. Command Center V2.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall