Agent skill · forcedotcom
service-omni-queue-members-assign
Use to bind agent users into a Salesforce Queue via GroupMember Data API POSTs, with SOQL-based idempotency (safe re-run — only inserts missing bindings). Binds either the generated demo agents (agent{1..N}.<suffix>@example.com) or an explicit list of real agents passed as usernames/User Ids. Triggers: add agents to a Case/Voice queue, assign agent users to a queue, populate queue membership for Omni routing. Do not use to create the queue (service-omni-queue-deploy), to create the agent users (service-omni-agent-users-create), or to assign permission sets (service-omni-permission-set-assign).
What it needs
About 3k tokens when loaded.
What this skill does
service-omni-queue-members-assign Bind N agent users into a Salesforce Queue via GroupMember Data API POSTs. Without queue membership, Omni-Channel routing sees an empty pool for the queue and never assigns work. Detection is SOQL-based (the same detect-then-POST shape as service-omni-queue-routing-config-deploy), so only missing memberships are created and the skill is safe to re-run. Agent users come from service-omni-agent-users-create, the queue from service-omni-queue-deploy, and the users' Omni permissions from service-omni-permission-set-assign. Inputs org-alias (required). queue-developer-name (optional, default CaseQueue). count (optional, default 3, range 1..10) — must match the agent user count; ignored in explicit mode. explicit-members-csv (optional 4th positional, or MEMBERUSERNAMESCSV / MEMBERUSERIDSCSV) — each token is a Username or a 15/18-char User Id; the count is derived from the list. Preconditions and safety Target org authenticated via sf CLI (My Domain URL), Service Cloud license, sf CLI ≥ 2.139.6. The executing user has PermissionsModifyAllData (standard on System Administrator). The agent users exist (service-omni-agent-users-create) and the queue exists (service-omni-queue-deploy); a missing user set or queue blocks with a pointer to the right skill (queues cannot be created via the Data API). The three-way safetowrite production guard applies — adding users to a production queue mis-routes real customer work, so it blocks with no override. Run verify-and-bind.sh runs the whole cycle: 1. Compute safetowrite; derive the 8-char org suffix. 2. Resolve the queue Group.Id by DeveloperName + Type='Queue'; block if missing. 3. Resolve the member set — generated mode queries User for agent{1..N}.<suffix>@example.com (block if any expected user is missing); explicit mode resolves each supplied token and requires every one to be an ACTIVE user. 4. Query existing GroupMember for the queue; compute the users not yet bound. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-queue-members-assign