Skip to main content
skill CX Codex

service-omni-supervisor-surface-deploy — Claude Code skill

service-omni-supervisor-surface-deploy — a skill for Claude Code populates the Omni-Channel Supervisor action and tab surface in Salesforce via the Data API. Runs when configuring supervisor panels.

Apache-2.0 102 installs ★ 1,183 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add forcedotcom/sf-skills --skill service-omni-supervisor-surface-deploy -a claude-code
Open on GitHub

What service-omni-supervisor-surface-deploy does

The skill inserts standard action and tab companion rows into an existing OmniSupervisorConfig using plain Data API requests against the parent identifier. Production guardrails automatically block write operations in non-sandbox environments unless safety checks pass. Prerequisites include sf CLI version 2.139.6 or higher, jq version 1.6+, python3 version 3.8+, an authenticated Salesforce org with a Service Cloud license, and a pre-existing configuration.

The script operates idempotently by checking existing records and inserting only missing types while appending new sequence numbers to DisplayOrder. Custom actions, AWS dashboards, and FlexiPage elements require manual setup through the Salesforce user interface.

What it helps with

  • populate Omni Supervisor action buttons and tabs
  • add Wallboard and Agents tabs to supervisor configuration
  • configure supervisor actions like Change Queues and Skills
  • perform idempotent surface updates via Data API

Example prompts for the agent

  • Deploy supervisor surface actions and tabs for production-org and config MainConfig
  • Check deployment plan for supervisor surface in staging-org using PLAN_ONLY=1
  • Populate standard Omni-Channel Supervisor tabs for my-org

How to install service-omni-supervisor-surface-deploy

1Skills CLI (Vercel)

npx skills add forcedotcom/sf-skills --skill service-omni-supervisor-surface-deploy -a claude-code

2Manually: put the files in place

~/.claude/skills/service-omni-supervisor-surface-deploy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/service-omni-supervisor-surface-deploy/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about service-omni-supervisor-surface-deploy

How to install service-omni-supervisor-surface-deploy in Claude Code?

Run npx skills add forcedotcom/sf-skills --skill service-omni-supervisor-surface-deploy -a claude-code, then reference ~/.claude/skills/service-omni-supervisor-surface-deploy/SKILL.md.

What does service-omni-supervisor-surface-deploy do?

It populates the Omni-Channel Supervisor action and tab surface on an existing configuration by inserting missing companion rows via the Data API.

What is needed to run service-omni-supervisor-surface-deploy?

It requires sf CLI ≥ 2.139.6, jq ≥ 1.6, python3 ≥ 3.8, an authenticated Salesforce target org, a Service Cloud license, and an existing OmniSupervisorConfig.

Source text

SKILL.md · Apache-2.0
---
name: service-omni-supervisor-surface-deploy
description: "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)."
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
  version: "1.0"
  domains: ["Service"]
  minApiVersion: "66.0"
  relatedSkills:
    - "service-omni-command-center-analyze"
    - "service-omni-supervisor-config-deploy"
    - "service-omni-supervisor-permset-assign"
  accessCheck: "OrgPermissions.LightningService"
  cliTools:
    - tool: ["jq"]
      semver: ">=1.6"
    - tool: ["python3"]
      semver: ">=3.8"
    - tool: ["sf"]
      semver: ">=2.139.6"
---

# service-omni-supervisor-surface-deploy

Populate the Omni-Channel Supervisor **surface** — the action buttons and tabs a supervisor sees — on an existing `OmniSupervisorConfig`. `OmniSupervisorConfigAction` and `OmniSupervisorConfigTab` are createable child sObjects (`OmniSupervisorConfigId`, a `*Type` picklist, and `DisplayOrder`), so the surface is populated with plain Data API inserts against the parent config's Id rather than by re-deploying the whole `OmniSupervisorConfig` metadata document. That keeps this leaf independent of `service-omni-supervisor-config-deploy` (which owns the user/queue companions inside the metadata file) and lets it run idempotently — it inserts only the types that are missing.

## Inputs

`bash scripts/deploy-and-report.sh <org-alias> [config_developer_name]`

- `org-alias` (required) — must resolve via `sf org display --target-org <alias>`.
- `config_developer_name` (optional) — the `OmniSupervisorConfig.DeveloperName` to populate. Omit it when the org has exactly one config; the skill resolves it. With multiple configs and no name, the skill blocks and lists them.

Env overrides (both CSV of picklist values; defaults are the reference-free standard set):

- `SUPERVISOR_ACTIONS` — default `AllAgents.ChangeQueues,AllAgents.ChangeSkills,AllAgents.ChangeGroups,AllAgents.AssignLearning,QueuesBacklog.ManageQueues`.
- `SUPERVISOR_TABS` — default `Wallboard,Agents,QueuesBacklog,AssignedWork,SkillsBacklog`.
- `PLAN_ONLY=1` — report intent (existing vs. requested) and stop before any write.

## Preconditions and safety

- Target org authenticated via `sf` CLI, Service Cloud license present, `sf` CLI ≥ 2.139.6.
- An `OmniSupervisorConfig` exists — provisioned by `service-omni-supervisor-config-deploy`. If none exists (or the named one is absent), the skill blocks with a `target_skill` pointer.
- **Production guardrail:** the script computes `safe_to_write` as `IsSandbox` OR `TrialExpirationDate != null` OR `OrganizationType` in {Developer Edition, Base Edition}, and blocks with no override when it is false.

## Run

```bash
bash scripts/deploy-and-report.sh <org-alias> [config_developer_name]
```

It resolves the parent config, reads the surface rows already present, inserts only the missing action/tab types (appending `DisplayOrder` after the current maximum), and emits JSON to stdout.

## Behavior

**Reference-free types only.** The companion rows expose no reference field, so only self-contained types can be inserted headlessly. The skill accepts the standard set (`SAFE_ACTIONS` / `SAFE_TABS` in `references/api-notes.md`) and **blocks up front** on any type that needs an external reference — `*.CustomAction`, `*.AWSDashboard`, `FlexipageType`, `AIAgents`, `AgentforceSDR` — pointing you to Setup. Requesting a type outside the supported vocabulary also blocks before any write.

**Idempotency.** The requested types are diffed against the rows already on the config; existing types are reported as `reused` and never re-inserted, missing types are inserted and reported as `created`. `status` is `created` when anything was inserted, otherwise `reused`. Re-running the skill unchanged makes no writes.

**Ordering.** New rows are appended: `DisplayOrder` starts one above the current maximum for that companion type, preserving any ordering already configured in Setup.

## Output contract

A single JSON object to stdout. `status` is one of `created`, `reused`, `blocked`, or (with `PLAN_ONLY=1`) `action_needed`. The object also carries `config` (`developer_name`, `id`), `actions` and `tabs` (each with `requested`, `created`, `reused`, `count`), `manual_actions`, and `blocking_issue` (`null` unless `status: blocked`).

Org-side spot-check:

```sql
SELECT OmniSupervisorActionType, DisplayOrder FROM OmniSupervisorConfigAction WHERE OmniSupervisorConfigId = :configId ORDER BY DisplayOrder
SELECT OmniSupervisorTabType,    DisplayOrder FROM OmniSupervisorConfigTab    WHERE OmniSupervisorConfigId = :configId ORDER BY DisplayOrder
```

## Limitations

- Populates only the reference-free standard action and tab types. Custom actions, FlexiPage tabs, AWS dashboards, and AI-agent surfaces need an external reference and must be configured in Setup.
- Does not create, rename, or delete the parent `OmniSupervisorConfig`, its user/queue companions, or supervisor users/permission sets.
- Does not remove surface rows — it only adds missing ones (no destructive reconciliation).

## References

| File | When to read |
|---|---|
| `references/api-notes.md` | The full `OmniSupervisorActionType` / `OmniSupervisorTabType` vocabulary, which types are reference-free, and companion-row insert semantics |

© forcedotcom · Apache-2.0 · forcedotcom/sf-skills

Similar skills

All skills for Backend and APIs →

From the same set232

The whole set →
service-omni-supervisor-config-deploy The service-omni-supervisor-config-deploy Claude Code skill deploys a classic Omni-Channel Supervisor configuration to Salesforce. It runs on requests to set up Omni Supervisor or the Supervisor Command Center. CX Codex +1 104installs service-omni-sidebar-configure service-omni-sidebar-configure — a skill for Claude Code enables and validates the pinned Omni-Channel sidebar on Lightning console apps. Configures the pinned utility view directly in CustomApplication metadata. CX Codex +1 103installs service-omni-presence-status-deploy The service-omni-presence-status-deploy Claude Code skill deploys Omni-Channel presence statuses. It runs for requests to create an Available status for Case, Incident, Messaging, or Voice, or to add the standard Busy status. CX Codex +1 103installs service-omni-base-settings-configure service-omni-base-settings-configure — a skill for Claude Code that configures Salesforce Omni-Channel base settings via the Metadata API. Deploys the five primary routing booleans required before setting up queues. CX Codex +1 103installs service-omni-supervisor-users-create The service-omni-supervisor-users-create Claude Code skill creates Omni-Channel supervisor users in a Salesforce org. It activates on requests to create or provision supervisor accounts. CX Codex +1 102installs service-omni-supervisor-permset-assign service-omni-supervisor-permset-assign — a skill for Claude Code that automates assigning the ContactCenterSupervisor permission set to users. Runs a verification and assignment script for Salesforce supervisor provisioning. CX Codex +1 102installs service-omni-presence-user-config-deploy The service-omni-presence-user-config-deploy Claude Code skill deploys an Omni presence configuration for agents. It sets decline handling and an ACW timer, then assigns the configuration to users. CX Codex +1 102installs service-omni-agent-users-create service-omni-agent-users-create — a skill for Claude Code creates Salesforce agent users for Omni-Channel setup and routing checks. It responds to requests for new, seeded, or missing demo agents. CX Codex +1 101installs

Project sponsors

Companies that keep this analytics open