service-omni-command-center-analyze — скилл для Claude Code
Скилл service-omni-command-center-analyze для Claude Code анализирует, выбрать ли Command Center V2 или классический Omni Supervisor, и рекомендует следующий шаг без изменений в организации.
Apache-2.0 132 установок ★ 1 183 обновлён 2026-10-23
npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a claude-codeЧто делает service-omni-command-center-analyze
Это точка входа в автоматизацию Command Center: скилл проверяет три независимых измерения — поддержку релиза, переключатель предпочтения CommandCenterForServiceV2 и разрешение CommandCenterForServiceUser для каждого супервизора. На основе этих сигналов возвращает одно из шести состояний: v2_ready, v2_permission_missing, v2_seed_incomplete, v2_available_not_enabled, legacy_selected или ambiguous (блокирующий случай, когда состояние невозможно доказать через публичные API).
Входные данные: алиас организации и опционально имя или ID супервизора. Скилл запускает только запросы SOQL и Tooling, не трогает конфигурацию. Требует sf CLI ≥ 2.139.6, лицензию Service Cloud и аутентификацию в целевой организации. На выходе — JSON с рекомендуемым следующим скиллом (например, service-omni-supervisor-config-deploy для классического пути) и детальными сигналами.
Какие задачи решает
- Выбрать между Command Center V2 и классическим Omni Supervisor перед конфигурацией
- Проверить готовность организации и супервизора к V2 без риска сломать настройки
- Диагностировать неполную подготовку V2 — несоответствие FlexiPage и вкладки
- Убедиться, что супервизор имеет нужное разрешение для V2
Примеры запросов агенту
- Какой инструмент должен использовать мой супервизор — Command Center V2 или классический Omni?
- Проверь готовность организации к Command Center V2 для юзера
[email protected] - Диагностируй Command Center: доступен ли V2 и какой следующий шаг после анализа?
Как установить service-omni-command-center-analyze
1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a claude-code2Вручную: положить файлы
~/.claude/skills/service-omni-command-center-analyze/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/service-omni-command-center-analyze/
1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a codex2Вручную: положить файлы
.agents/skills/service-omni-command-center-analyze/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a cursor2Вручную: положить файлы
.cursor/skills/service-omni-command-center-analyze/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install forcedotcom/sf-skills skills/service-omni-command-center-analyze2Вручную: положить файлы
.github/skills/service-omni-command-center-analyze/SKILL.md1Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a gemini-cli2Командой платформы
gemini skills install https://github.com/forcedotcom/sf-skills --path skills/service-omni-command-center-analyzeВручную: положить файлы
.devin/skills/service-omni-command-center-analyze/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о service-omni-command-center-analyze
Как установить service-omni-command-center-analyze в Claude Code?
Запусти npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a claude-code, затем открой ~/.claude/skills/service-omni-command-center-analyze/SKILL.md.
Что делает service-omni-command-center-analyze?
Анализирует, готова ли организация к Command Center V2 или нужно использовать классический Omni Supervisor, и рекомендует следующий скилл. Работает только на чтение, не меняет конфигурацию.
Что нужно, чтобы запустить скилл?
Организация с лицензией Service Cloud, аутентификация в sf CLI версии ≥ 2.139.6 и установленные jq ≥ 1.6 и python3 ≥ 3.8. Минимальный API Salesforce — 66.0.
Исходный текст
SKILL.md · Apache-2.0
---
name: service-omni-command-center-analyze
description: "Use to analyze whether an org should use Command Center for Service V2 or classic Omni Supervisor and recommend the next action without making changes. Triggers: detect Command Center V2 versus classic, check supervisor readiness, choose a supervisor experience, diagnose Command Center availability, assess Omni Supervisor setup. Do not use to enable V2, assign permissions, or deploy configuration."
allowed-tools: Bash Read Grep Glob
metadata:
version: "1.0"
domains: ["Service"]
minApiVersion: "66.0"
relatedSkills:
- "service-omni-channel-setup-coordinate"
- "service-omni-supervisor-config-deploy"
accessCheck: "OrgPermissions.LightningService"
cliTools:
- tool: ["jq"]
semver: ">=1.6"
- tool: ["python3"]
semver: ">=3.8"
- tool: ["sf"]
semver: ">=2.139.6"
---
# service-omni-command-center-analyze
Decide, **without changing anything**, which supervisor experience an org should use and what to do next. Command Center for Service V2 is gated on three independent dimensions — org **capability** (release gater), the **`CommandCenterForServiceV2` org preference** (whose ON-flip seeds the `CommandCenterForServiceV2_L` FlexiPage and registers the V2 tab), and the per-supervisor **`CommandCenterForServiceUser`** permission. A single boolean cannot express that, so this skill returns an explicit **state** plus the recommended follow-up skill (e.g. `service-omni-supervisor-config-deploy` for the classic path). It is the entry point of the Command Center flow — `service-omni-channel-setup-coordinate` runs it first — and is safe to run on any org, including production, because it only reads.
## Inputs
```bash
bash scripts/analyze.sh <org-alias> [supervisor_username_or_id]
```
- `org-alias` (required).
- `supervisor_username_or_id` (optional). A Username (`…@…`) or 15/18-char User Id (`005…`). When given, the per-user `CommandCenterForServiceUser` permission is evaluated; when omitted, the permission dimension is reported as not-checked and readiness is org-level only.
## Preconditions and safety
- Target org authenticated via `sf` CLI, Service Cloud license, `sf` CLI ≥ 2.139.6.
- **Read-only** — no `safe_to_write` guard is needed; the skill issues only SOQL/Tooling queries.
## Run
`analyze.sh` gathers observable signals and maps them to a state:
| Signal | Source | Meaning |
|---|---|---|
| V2 capability | `SELECT Id FROM PermissionSet WHERE PermissionsCommandCenterForServiceUser = true` probe | If the user-permission column does not exist on the org schema, V2 is not available. |
| Seeded FlexiPage | Tooling: `FlexiPage` where `DeveloperName='CommandCenterForServiceV2_L'` | Present ⇒ the org preference was enabled and the page was seeded. |
| V2 tab | `TabDefinition` (best-effort) | Cross-checks the seed; a seed/tab mismatch indicates a partial provision. |
| Supervisor permission | `PermissionSetAssignment` joined on `PermissionSet.PermissionsCommandCenterForServiceUser` | Whether the named supervisor can use V2. |
| Legacy config | Tooling: `OmniSupervisorConfig` count | Informational for the classic path. |
## Behavior
**States and recommended next action:**
| State | Meaning | Recommended skill |
|---|---|---|
| `v2_ready` | Capability + seed present (and supervisor has permission, if checked) | verify only (coordinator proceeds to V2 verification) |
| `v2_permission_missing` | V2 enabled but the named supervisor lacks `CommandCenterForServiceUser` | Manual — assign `CommandCenterForServiceUser` (headless-capable via PermissionSet; packaging pending) |
| `v2_seed_incomplete` | Capability present but the FlexiPage/tab provisioning is inconsistent | Manual — re-check in Setup → Omni-Channel → Supervisor Settings (no supported public write API) |
| `v2_available_not_enabled` | Org supports V2 but the preference is off | Manual — enable in Setup → Omni-Channel → Supervisor Settings (no supported Metadata/Tooling write API) |
| `legacy_selected` | V2 capability absent | `service-omni-supervisor-config-deploy` |
| `ambiguous` | A required signal could not be read through a supported API | none — **blocks**, do not guess |
`ambiguous` is the only state that exits non-zero: the review's rule is to block rather than infer when state cannot be proven read-only. All other states exit 0 with `status:"detected"`.
## Output contract
A single JSON object: `status` (`detected` | `blocked`), `state` (one of the six above), `recommended_action`, `recommended_skill`, `signals` (`v2_capability`, `seed_flexipage_present`, `v2_tab_present`, `supervisor{identifier,checked,has_command_center_permission}`, `legacy_omnisupervisorconfig_count`), `manual_actions`, `blocking_issue`.
## Limitations
- The `CommandCenterForServiceV2` org preference has no supported public read; its state is **inferred** from the seeded FlexiPage (the platform seeds on the ON-flip). This is called out in `signals` and is why a bare capability-without-seed reads as `v2_available_not_enabled`.
- The release gater cannot be read directly; capability is inferred from the presence of the user-permission column on the org schema.
- Tab detection is best-effort; when the tab query cannot run, `v2_tab_present` is `"unknown"` and state is derived from the remaining signals.
- Read-only: it never enables V2, seeds pages, assigns permissions, or deploys config.
## References
| File | When to read |
|---|---|
| `references/api-notes.md` | The three-dimensional V2 gate, why each signal is a proxy, and the exact queries used |
© forcedotcom · Apache-2.0 · forcedotcom/sf-skills