forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-presence-user-config-deploy
service-omni-presence-user-config-deploy
VerifiedUse to deploy an Omni PresenceUserConfig (presence configuration) as one whole-record Metadata write with the decline/ACW fields set consistently: Auto-Accept off, Decline on, Decline Reason on (with a PresenceDeclineReason deployed in the same package), and an After-Conversation-Work wrap-up timer. Agents are assigned by username. Idempotent via the Metadata API files[].state signal. Triggers: create presence configuration, enable decline + decline reason + ACW wrap-up timer for agents, assign presence config to users. Do not use for ServicePresenceStatus (separate skill), for permission-set access to statuses, or to set the channel-level ACW timer on a ServiceChannel.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| references/api-notes.md | markdown | 3.0 KB |
| scripts/deploy-and-report.shexecutable | script | 12.6 KB |
| scripts/tests/_bootstrap.py | script | 4.3 KB |
| scripts/tests/test_presence_user_config_contracts.pyexecutable | script | 5.9 KB |
references/api-notes.md
View on GitHub# API notes — service-omni-presence-user-config-deploy
## Why one whole-record Metadata write
`PresenceUserConfig` has **cross-field validators** that make field-by-field editing fragile — the
correct combination only validates when the whole record is written together:
- `enableAutoAccept` is allowed only when `enableDecline=false`, and vice versa. They are mutually
exclusive; this skill sets Auto-Accept **off** and Decline **on**.
- `enableDeclineReason=true` is permitted only when decline reasons are enabled (Decline on) and at
least one `declineReasons` entry is present.
- `presenceStatusOnDecline` is available only when `enableDecline=true`.
- The ACW timer is paired: `hasAfterConvoWorkTimer=true` **requires** `afterConvoWorkMaxTime`
(10–3600 s). Optional extension uses `hasAcwExtensionEnabled` + `acwExtensionDuration` +
`maxExtensions` (not set by this skill).
Deploying the record as a single Metadata component applies all of these atomically.
## Required fields + XSD element order
`capacity` and `label` are required. Metadata API enforces element order; the emitted document
follows the schema sequence:
```text
acwExtensionDuration, afterConvoWorkMaxTime, assignments, capacity, declineReasons,
enableAutoAccept, enableDecline, enableDeclineReason, enableDisconnectSound, enableRequestSound,
hasAcwExtensionEnabled, hasAfterConvoWorkTimer, interruptibleCapacity, label, maxExtensions,
presenceStatusOnDecline, presenceStatusOnPushTimeout, userDisplayName
```
This skill emits: `afterConvoWorkMaxTime → assignments → capacity → declineReasons →
enableAutoAccept → enableDecline → enableDeclineReason → hasAfterConvoWorkTimer → label →
[presenceStatusOnDecline]` — all ascending in the sequence above.
## Decline reason packaging
`declineReasons` references a `PresenceDeclineReason` by its DeveloperName (fullName). The two
components are deployed in the **same package** so the reference resolves in one deploy; a
standalone config referencing a not-yet-deployed reason would fail. `PresenceDeclineReason` itself
carries only a `label`.
## Assignments
`assignments/users/user` takes **usernames**, not User Ids — the skill resolves any `005…` Ids to
usernames first. A redeploy declares the full assignment set for this config; the skill does not
remove users it did not add. The `<assignments>` block is omitted entirely when no agents are given
(a valid, unassigned config).
## Idempotency signal
Per-component `files[].state` from the Metadata API is authoritative: `Unchanged` → reused,
`Changed` → updated, `Created` → created. The deploy runs `--async` and polls
`sf project deploy report` to a terminal state; a job that never reaches one is reported as blocked
rather than assumed successful.
## Out of scope: channel-level ACW
The steel thread also mentions an After-Conversation-Work timer on the **Voice `ServiceChannel`**.
That is a different field on a different object (the channel, not the presence config) and is not set
here — this skill governs the agent-level presence/wrap-up behavior only.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |