service-omni-skills-based-routing-configure — скилл для Claude Code
Скилл service-omni-skills-based-routing-configure для Claude Code связывает Omni Skill с активными пользователями агентов. Запускается при настройке маршрутизации Omni по навыкам.
Apache-2.0 106 установок ★ 1 183 обновлён 2026-10-23
npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a claude-codeЧто делает service-omni-skills-based-routing-configure
Скилл проверяет, создан ли Omni Skill, и назначает его пользователям активных агентов через связь SkillUser. Уже существующие навыки и назначения он оставляет, создавая только недостающие связи. Повторный запуск не дублирует записи.
Для работы нужны аутентифицированный sf CLI версии 2.139.6 или новее, лицензия Service Cloud и включённая маршрутизация по навыкам в настройках Omni-Channel. Также нужны имена или идентификаторы существующих активных агентов. За один запуск настраивается один навык.
Скилл не создаёт пользователей агентов, очереди и правила WorkSkillRouting. Уровень SkillUser.SkillLevel остаётся платформенным значением по умолчанию.
Какие задачи решает
- создать Omni Skill, если его ещё нет
- назначить навык активным пользователям агентов
- добавить только недостающие связи
SkillUser - найти агентов с неудавшимся назначением
Примеры запросов агенту
- Настрой маршрутизацию по навыку
Omni_Demo_Voiceдля пользователейagent_members.csvв организацииmy-org. - Свяжи существующий Omni Skill с активными агентами
005000000000001и005000000000002вmy-org. - Исправь недостающие назначения навыка
Omni_Demo_Voiceдля активных агентов организацииmy-org.
Как установить service-omni-skills-based-routing-configure
1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a claude-code2Вручную: положить файлы
~/.claude/skills/service-omni-skills-based-routing-configure/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/service-omni-skills-based-routing-configure/
1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a codex2Вручную: положить файлы
.agents/skills/service-omni-skills-based-routing-configure/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a cursor2Вручную: положить файлы
.cursor/skills/service-omni-skills-based-routing-configure/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install forcedotcom/sf-skills skills/service-omni-skills-based-routing-configure2Вручную: положить файлы
.github/skills/service-omni-skills-based-routing-configure/SKILL.md1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a gemini-cli2Командой платформы
gemini skills install https://github.com/forcedotcom/sf-skills --path skills/service-omni-skills-based-routing-configureВручную: положить файлы
.devin/skills/service-omni-skills-based-routing-configure/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о service-omni-skills-based-routing-configure
Как установить service-omni-skills-based-routing-configure в Claude Code?
Выполни npx skills add forcedotcom/sf-skills --skill service-omni-skills-based-routing-configure -a claude-code. Файл скилла появится по пути ~/.claude/skills/service-omni-skills-based-routing-configure/SKILL.md.
Что делает service-omni-skills-based-routing-configure?
Он создаёт Omni Skill при необходимости и связывает его с пользователями активных агентов через SkillUser. Существующие записи повторно использует.
Что нужно для работы service-omni-skills-based-routing-configure?
Нужны аутентифицированный sf CLI версии 2.139.6 или новее, лицензия Service Cloud, включённая маршрутизация по навыкам Omni-Channel и существующие активные пользователи агентов.
Исходный текст
SKILL.md · Apache-2.0
---
name: service-omni-skills-based-routing-configure
description: "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."
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
version: "1.0"
domains: ["Service"]
minApiVersion: "66.0"
relatedSkills:
- "service-omni-agent-users-create"
- "service-omni-base-settings-configure"
accessCheck: "OrgPermissions.LightningService"
cliTools:
- tool: ["jq"]
semver: ">=1.6"
- tool: ["python3"]
semver: ">=3.8"
- tool: ["sf"]
semver: ">=2.139.6"
---
# 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
```bash
bash scripts/configure-and-report.sh <org-alias> <skill_developer_name> [agent_members_csv] [skill_master_label]
```
- `org-alias` (required).
- `skill_developer_name` (required). The Omni `Skill` DeveloperName to ensure and bind (e.g. `Omni_Demo_Voice`).
- `agent_members_csv` (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 `AGENT_MEMBERS_CSV`. When omitted, the skill blocks (it will not guess which agents to skill).
- `skill_master_label` (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 `safe_to_write` 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. A concurrent `DUPLICATE_VALUE` is reconciled as reused.
## Behavior
**Idempotent + non-destructive.** Existing skills and bindings are reused; the skill never deletes or reassigns anything it did not create, so re-runs converge without duplication. Only **active** users are resolved — an inactive user cannot be routed work, so it is reported rather than silently skilled.
**Partial safety.** If some bindings succeed and others fail, the status is `partial` with per-agent errors in `blocking_issue`; the successful bindings are left in place (each junction is an independent write).
## Output contract
A single JSON object: `status` ∈ `configured` | `reused` | `partial` | `blocked`, `skill` (`{developer_name, id, state}`), `agents` (array of `{username, user_id, skill_binding_id, skill_binding_state}`), `created_counts`, `reused_counts`, `manual_actions`, `blocking_issue`.
- `reused` — skill and all bindings already existed.
- `configured` — at least one component created and all requested bindings now exist.
- `partial` / `blocked` — see `blocking_issue`; `manual_actions` names the prerequisite skill when the cause is a missing precondition.
## Limitations
- One skill per invocation; run again per skill an agent set needs.
- Does not author `WorkSkillRouting` rules or field-based skill criteria — that is a separate skill.
- Does not create agent users, queues, or presence configuration.
- `SkillUser.SkillLevel` is left at the platform default; forking the DML body is required to set explicit proficiency.
## References
| File | When to read |
|---|---|
| `references/api-notes.md` | Skill metadata vs Skill sObject, the SkillUser agent-binding model, and SBR base-setting prerequisites |
| `scripts/tests/test_sbr_contracts.py` | When validating changes — run `python3 scripts/tests/test_sbr_contracts.py` from this skill directory |
© forcedotcom · Apache-2.0 · forcedotcom/sf-skills