service-omni-presence-status-deploy — Claude Code skill: install
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.
Apache-2.0 103 installs ★ 1,183 updated 2026-10-23
npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a claude-codeWhat service-omni-presence-status-deploy does
The skill deploys an Available_<X> status for the selected object and creates Busy only when the org does not already have one. Each Available status is tied to that object’s ServiceChannel: for example, Available_Case uses Cases, while Available_Voice uses sfdc_phone. Both are handled in one Metadata API deploy. Existing presence statuses are left untouched.
The target org must be authenticated, have a Service Cloud license, and use sf version 2.139.6 or later and jq version 1.6 or later. Omni-Channel base settings must be enabled, and the selected object’s ServiceChannel must exist. Incident also needs Incident Management enabled; MessagingSession requires Enhanced Messaging. The accepted object types are Case, Incident, MessagingSession, and VoiceCall; omitting the argument selects Case. The skill does not configure PresenceUserConfig capacity or decline reasons, and custom status designs are outside its scope.
What it helps with
- create an Available status for a supported object
- bind an availability status to its ServiceChannel
- add Busy only when the org lacks it
- deploy the presence statuses in one Metadata API call
Example prompts for the agent
- Deploy the Omni-Channel Available status for
Caseto orgmy-org. - Set up agent availability for
MessagingSessionin orgmy-org. - Add the standard Busy and Available statuses for
VoiceCallin orgmy-org.
How to install service-omni-presence-status-deploy
1Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a claude-code2Manually: put the files in place
~/.claude/skills/service-omni-presence-status-deploy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/service-omni-presence-status-deploy/
1Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a codex2Manually: put the files in place
.agents/skills/service-omni-presence-status-deploy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a cursor2Manually: put the files in place
.cursor/skills/service-omni-presence-status-deploy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install forcedotcom/sf-skills skills/service-omni-presence-status-deploy2Manually: put the files in place
.github/skills/service-omni-presence-status-deploy/SKILL.md1Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a gemini-cli2Platform CLI
gemini skills install https://github.com/forcedotcom/sf-skills --path skills/service-omni-presence-status-deployManually: put the files in place
.devin/skills/service-omni-presence-status-deploy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about service-omni-presence-status-deploy
How do I install service-omni-presence-status-deploy in Claude Code?
Run npx skills add forcedotcom/sf-skills --skill service-omni-presence-status-deploy -a claude-code. The skill file is installed at ~/.claude/skills/service-omni-presence-status-deploy/SKILL.md.
What does service-omni-presence-status-deploy do?
It deploys an Available status linked to the channel for Case, Incident, MessagingSession, or VoiceCall. It adds Busy only if the org does not already have that status.
What does service-omni-presence-status-deploy require?
It requires an authenticated Salesforce org, a Service Cloud license, sf 2.139.6 or later, and jq 1.6 or later. Omni-Channel base settings and the target ServiceChannel must be in place; Incident needs Incident Management, while MessagingSession needs Enhanced Messaging.
Source text
SKILL.md · Apache-2.0
---
name: service-omni-presence-status-deploy
description: "Create the standard Available and Busy presence statuses needed for Omni-Channel routing. TRIGGER when users ask to deploy Omni presence statuses, configure agent availability, deploy Omni status metadata, create an Available status for Case, Incident, Messaging, or Voice, or add the standard Busy status. DO NOT TRIGGER for custom status designs, unsupported objects, or PresenceUserConfig capacity."
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
version: "1.0"
domains: ["Service"]
minApiVersion: "66.0"
relatedSkills:
- "service-omni-base-settings-configure"
- "service-omni-channel-setup-coordinate"
- "service-omni-permission-set-assign"
- "service-omni-service-channel-configure"
accessCheck: "OrgPermissions.LightningService"
cliTools:
- tool: ["jq"]
semver: ">=1.6"
- tool: ["sf"]
semver: ">=2.139.6"
---
# service-omni-presence-status-deploy
Deploy the sObject-specific `Available_<X>` ServicePresenceStatus bound to that sObject's ServiceChannel, and ensure a universal `Busy` status exists, in one atomic Metadata API deploy. Every Omni agent needs an "available for work" status carrying a channel (so incoming work routes) and an "off-work" status (so they can step away). A presence status binds to exactly one ServiceChannel by DeveloperName, so each routing target needs its own Available status. It pairs with `service-omni-permission-set-assign`, which grants agents access to the statuses this skill deploys, and is invoked once per routing target by `service-omni-channel-setup-coordinate`.
| Target sObject | Available status | Bound channel |
|---|---|---|
| `Case` | `Available_Case` | `Cases` |
| `Incident` | `Available_Incident` | `Incidents` |
| `MessagingSession` | `Available_Messaging` | `sfdc_livemessage` |
| `VoiceCall` | `Available_Voice` | `sfdc_phone` |
**Busy is UI-defined, not metadata-defined.** The Omni "Busy vs Online" option is not expressible via the Metadata API — a `ServicePresenceStatus` carries only `<label>` and `<channels>`, and a status with no channels is treated as busy. The conventional busy DeveloperName is simply `Busy`, and most orgs already have one, so this skill reuses an existing `Busy` and deploys the bundled asset only when none exists. A busy status is not required to receive work — the Available status carrying the channel is what routes it.
## Inputs
```bash
bash scripts/deploy-and-report.sh <org-alias> [Case|Incident|MessagingSession|VoiceCall]
```
- `org-alias` (required).
- `sobject_type` (optional, default `Case`).
## Preconditions and safety
- Target org authenticated via `sf` CLI (My Domain URL), Service Cloud license, `sf` CLI ≥ 2.139.6.
- Omni-Channel base settings enabled (`service-omni-base-settings-configure`) — otherwise the deploy fails with `INVALID_TYPE`.
- The target sObject's ServiceChannel exists (`service-omni-service-channel-configure`) — otherwise the deploy fails with `Value '<channel>' is not valid`. `Incident` requires the Incident Management feature enabled; `MessagingSession` requires Enhanced Messaging.
- The three-way `safe_to_write` production guard applies.
## Run
`deploy-and-report.sh` deploys the `Available_<X>` status (and `Busy` only when the org has none) in one Metadata API call, then maps the per-component `files[].state` to a skill status:
- `reused` — every component `Unchanged`.
- `updated` — any component `Changed`, none `Created`.
- `created` — any component `Created`.
There is no separate detect step — Salesforce's `files[].state` is authoritative. The deploy uses explicit `--metadata` flags (never `--source-dir`) so unrelated assets cannot piggyback.
## Behavior
**Reuse over redeploy.** An existing `Busy` is detected and left untouched; only a missing one is deployed. The skill never deletes or overwrites presence statuses it did not deploy — orgs often carry other custom statuses (`Omni_OnBreak`, `availableForMiaw`).
**Schema.** The XML omits `<statusType>` (removed in v66; online/busy is inferred from the presence of `<channels>`), and the skill never SOQL-queries `StatusType` (not queryable on v66 — only Id, DeveloperName, MasterLabel are reliable). `Available_Messaging` binds the standard `sfdc_livemessage` channel that Enhanced Messaging always ships.
## Output contract
A single JSON object with `status` ∈ `created` | `reused` | `updated` | `blocked`, `sobject_type`, a `presence_statuses` array (each with `developer_name`, `label`, `channels`, `state`, and — for `Busy` — `reused_existing`), `deploy_id`, `manual_actions`, and `blocking_issue`.
- `blocked` — deploy failed (missing prereq, schema mismatch, or org error); `manual_actions` names the prerequisite skill to run and `blocking_issue` is an operator-friendly translation of the Salesforce error.
- `deploy_id` is populated on every run (Salesforce issues one even for no-op deploys).
## Limitations
- Deploys only the `Available_<X>` + `Busy` pair — custom statuses require forking the `assets/servicePresenceStatuses/*.xml`.
- Only `Case`, `Incident`, `MessagingSession`, `VoiceCall` — extend by adding a dispatcher branch and a matching asset.
- Does not configure `PresenceUserConfig` capacity or decline reasons, and never deletes existing statuses.
## References
| File | When to read |
|---|---|
| `assets/package.xml` | Load when preparing the explicit Metadata API deployment for the selected Available status and the optional Busy status |
| `references/api-notes.md` | On unexpected deploy behavior — the v66 XML schema (no `statusType`), channel-binding rules, and MessagingSession-specific notes |
© forcedotcom · Apache-2.0 · forcedotcom/sf-skills