Agent skill · forcedotcom
service-omni-skills-based-routing-configure
Use to make agents routable by Omni skills-based routing: ensure an Omni Skill exists, then assign it to each active agent through the classic Omni-Channel SkillUser junction. Idempotent — existing skills and user bindings are reused, and only missing bindings are created. Works on Service Cloud orgs without requiring Field Service. Triggers: set up skills-based routing agents, assign Omni skills to agents, make agents skill-routable, create an Omni skill and bind users, repair missing agent skill assignments. Do not use to author WorkSkillRouting rules, create agent users, or configure queues.
What it needs
About 3k tokens when loaded.
What this skill does
service-omni-skills-based-routing-configure Make agents routable by Omni skills-based routing (SBR). A routable agent needs the Skill and a SkillUser junction assigning that skill to the agent's user. SkillUser is the classic Omni-Channel model written by Setup > Skills > Assign Users and evaluated when work has skill requirements. This skill ensures both, idempotently, for one skill across a set of active agent users. ServiceResource and ServiceResourceSkill are the Field Service skill model. On a plain Service Cloud org, ServiceResource.IsActive is not writable or queryable, so a newly created resource remains inactive and the junction is rejected. This skill therefore uses the supported, license-appropriate SkillUser path. Inputs org-alias (required). skilldevelopername (required). The Omni Skill DeveloperName to ensure and bind (e.g. OmniDemoVoice). agentmemberscsv (optional). Comma-separated agents to make skill-routable — each token a Username (…@…) or a 15/18-char User Id (005…). May also be supplied via AGENTMEMBERSCSV. When omitted, the skill blocks (it will not guess which agents to skill). skillmasterlabel (optional). MasterLabel used only when the skill must be created; defaults to a title-cased form of the DeveloperName. Preconditions and safety Target org authenticated via sf CLI, Service Cloud license, sf CLI ≥ 2.139.6. Omni-Channel base settings enabled with skills-based routing turned on (service-omni-base-settings-configure). The named agents exist and are active (service-omni-agent-users-create). The three-way safetowrite production guard applies. Run configure-and-report.sh proceeds in two idempotent phases, each detect-before-write: 1. Skill — query Skill by DeveloperName. Present → reused; absent → deploy a Skill component via the Metadata API and re-query for its Id. 2. SkillUser — query existing SkillUser records for the Skill and resolved users, then create only missing (SkillId, UserId) bindings via REST DML. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-skills-based-routing-configure