forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-base-settings-configure
service-omni-base-settings-configure
VerifiedUse to enable the five Omni-Channel base settings on a Salesforce org via the Metadata API. The canonical writer scripts/configure-and-report.sh detects, deploys, and re-verifies in one call (run mode) or detects only (plan mode); it is idempotent (deploys only when a toggle is false or missing) and guards writes with a sandbox/CDO/trial/DE safe_to_write check. It always surfaces the UI-only login-behavior gap in its report. Triggers: enable Omni-Channel, turn on Omni base settings, configure OmniChannelSettings, deploy Settings:OmniChannel. Do not use to configure downstream Omni entities (queues, presence, permissions — use the entity-specific skill) or to deploy other Settings types (use platform-metadata-deploy).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| assets/force-app/main/default/settings/OmniChannel.settings-meta.xml | config | 448 B |
| assets/package.xml | config | 230 B |
| assets/sfdx-project.json | config | 244 B |
| references/api-notes.md | markdown | 5.4 KB |
| scripts/configure-and-report.shexecutable | script | 6.7 KB |
| scripts/detect-existing.shexecutable | script | 2.4 KB |
scripts/detect-existing.sh
View on GitHub#!/usr/bin/env bash
# detect-existing.sh - read-only probe of OmniChannelSettings (five toggle values + all_enabled); deterministic, no side effects. Args, output, exit codes: SKILL.md.
set -euo pipefail
if [ $# -lt 1 ]; then
echo '{"error":"Missing required argument: org-alias","usage":"bash detect-existing.sh <org-alias>"}' >&2
exit 1
fi
ORG="$1"
# Verify org is authenticated (fail fast, do not retrieve if org auth is broken)
if ! sf org display --target-org "$ORG" --json >/dev/null 2>&1; then
echo "{\"error\":\"Org alias '$ORG' is not authenticated. Run: sf org login web -a $ORG -r <my-domain-url>\"}" >&2
exit 1
fi
# Retrieve Settings:OmniChannel into a per-invocation temp DX project.
# Metadata retrieve is slow (~1-2 min); this is expected and unavoidable.
WORK="$(mktemp -d)"
trap 'rm -rf "$WORK"' EXIT
cat > "$WORK/sfdx-project.json" <<'EOF'
{"packageDirectories":[{"path":"force-app","default":true}],"sourceApiVersion":"66.0"}
EOF
mkdir -p "$WORK/force-app/main/default"
if ! (cd "$WORK" && sf project retrieve start --target-org "$ORG" --metadata "Settings:OmniChannel" --json >/dev/null 2>&1); then
echo "{\"error\":\"Metadata retrieve failed for Settings:OmniChannel on org '$ORG'. This is often transient (UNKNOWN_EXCEPTION) - retry once.\"}" >&2
exit 1
fi
SETTINGS_RELATIVE_PATH="force-app/main/default/settings/OmniChannel.settings-meta.xml"
XML="$WORK/$SETTINGS_RELATIVE_PATH"
if [ ! -f "$XML" ]; then
echo "{\"error\":\"Retrieve succeeded but expected file not found: $SETTINGS_RELATIVE_PATH. Org may not have Omni-Channel provisioned.\"}" >&2
exit 1
fi
# Parse each toggle from the retrieved XML; a missing element means absent (treat as false).
parse_toggle() {
local name="$1"
local val
val=$(grep -oE "<${name}>(true|false)</${name}>" "$XML" | head -1 | sed -E "s|</?${name}>||g" || true)
if [ "$val" = "true" ]; then echo true; else echo false; fi
}
T1=$(parse_toggle enableOmniAutoLoginPrompt)
T2=$(parse_toggle enableOmniChannel)
T3=$(parse_toggle enableOmniSecondaryRoutingPriority)
T4=$(parse_toggle enableOmniSkillsRouting)
T5=$(parse_toggle enableOmniStatusCapModel)
ALL=false
if [ "$T1" = "true" ] && [ "$T2" = "true" ] && [ "$T3" = "true" ] && [ "$T4" = "true" ] && [ "$T5" = "true" ]; then
ALL=true
fi
cat <<EOF
{
"enableOmniAutoLoginPrompt": $T1,
"enableOmniChannel": $T2,
"enableOmniSecondaryRoutingPriority": $T3,
"enableOmniSkillsRouting": $T4,
"enableOmniStatusCapModel": $T5,
"all_enabled": $ALL
}
EOF
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 |