New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Service Omni Command Center Analyze

by forcedotcom in forcedotcom/sf-skills

A skill your agent uses to analyze whether an org should use Command Center for Service V2 or classic Omni Supervisor and recommend the next action without making changes.

Apache-2.0Auto-check: notes

Install Service Omni Command Center Analyze

skills CLI
$ npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills service-omni-command-center-analyze --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/service-omni-command-center-analyze .claude/skills/service-omni-command-center-analyze && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
service-omni-command-center-analyze
GitHub stars
1.1k
Token cost
~1.4k tokens
SKILL.md length
535 words
Files
5 (incl. scripts, references)
Skills in repo
252
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses to analyze whether an org should use Command Center for Service V2 or classic Omni Supervisor and recommend the next action without making changes.

  • Analyze whether an org should use Command Center for Service V2
  • SKILL.md covers Inputs, Preconditions and safety, Run and Behavior, plus 3 more sections
  • Runs Python and Shell scripts from its folder; calls bash
  • Classic Omni Supervisor and recommend the next action without making changes

What it does

Service Omni Command Center Analyze is an agent skill from forcedotcom/sf-skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/api-notes.md`, `scripts/analyze.sh` and `scripts/tests/_bootstrap.py`).

The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • Analyze whether an org should use Command Center for Service V2
  • Classic Omni Supervisor and recommend the next action without making changes
  • Assign permissions
  • Deploy configuration

Example prompts

  • “/service-omni-command-center-analyze”

Requirements

  • Python 3
  • A Bash shell
  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob

What it can do on your machine

Read from SKILL.md and the folder at commit 4bbae5c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Service Omni Command Center Analyze loads about 1.4k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 535 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit 4bbae5c, republished under its Apache-2.0 licence (© forcedotcom). 535 words, ~1,400 tokens.

Download SKILL.mdSave it as .claude/skills/service-omni-command-center-analyze/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
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
metadata.domains
Service
metadata.minApiVersion
66.0
metadata.relatedSkills
service-omni-channel-setup-coordinate, service-omni-supervisor-config-deploy

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:

SignalSourceMeaning
V2 capabilitySELECT Id FROM PermissionSet WHERE PermissionsCommandCenterForServiceUser = true probeIf the user-permission column does not exist on the org schema, V2 is not available.
Seeded FlexiPageTooling: FlexiPage where DeveloperName='CommandCenterForServiceV2_L'Present ⇒ the org preference was enabled and the page was seeded.
V2 tabTabDefinition (best-effort)Cross-checks the seed; a seed/tab mismatch indicates a partial provision.
Supervisor permissionPermissionSetAssignment joined on PermissionSet.PermissionsCommandCenterForServiceUserWhether the named supervisor can use V2.
Legacy configTooling: OmniSupervisorConfig countInformational for the classic path.
Show full SKILL.md (277 more words)Show less

Behavior

States and recommended next action:

StateMeaningRecommended skill
v2_readyCapability + seed present (and supervisor has permission, if checked)verify only (coordinator proceeds to V2 verification)
v2_permission_missingV2 enabled but the named supervisor lacks CommandCenterForServiceUserManual — assign CommandCenterForServiceUser (headless-capable via PermissionSet; packaging pending)
v2_seed_incompleteCapability present but the FlexiPage/tab provisioning is inconsistentManual — re-check in Setup → Omni-Channel → Supervisor Settings (no supported public write API)
v2_available_not_enabledOrg supports V2 but the preference is offManual — enable in Setup → Omni-Channel → Supervisor Settings (no supported Metadata/Tooling write API)
legacy_selectedV2 capability absentservice-omni-supervisor-config-deploy
ambiguousA required signal could not be read through a supported APInone — 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

FileWhen to read
references/api-notes.mdThe three-dimensional V2 gate, why each signal is a proxy, and the exact queries used

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in skills/service-omni-command-center-analyze of forcedotcom/sf-skills.

  • SKILL.md
  • references/api-notes.md
  • scripts/analyze.sh
  • scripts/tests/_bootstrap.py
  • scripts/tests/test_command_center_analyze_contracts.py

Open the folder on GitHubat commit 4bbae5c

Compare with similar skills

Service Omni Command Center Analyze next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Service Omni Command Center Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Service Omni Command Center Analyze this skillforcedotcom/sf-skills1.1k—~1.4kAutomated safety check: NotesApache-2.0
Gemini Omnicalesthio/OpenMontage66k—~2.1kAutomated safety check: NotesAGPL-3.0
Command Center UIsickn33/agentic-awesome-skills47k1 repos~3.1kAutomated safety check: PassMIT
Omnifajarhide/omni366—~1.1kAutomated safety check: PassApache-2.0
Cue Omni Readeriflytek/skillhub5.2k—~1.5kAutomated safety check: PassMIT
Vllm Omni Testvllm-project/vllm-omni7.1k—~17kAutomated safety check: PassApache-2.0

Similar skills

  • Gemini Omni

    calesthio/OpenMontage

    Generate and conversationally edit short videos with Google Gemini Omni Flash (gemini-omni-flash-preview).

    66k GitHub stars~2.1k tokensUpdated 7 days ago
    Media & CreativeAuto-check: notes

  • Command Center UI

    sickn33/agentic-awesome-skills

    Web and App implementation guide for Command Center UI. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~3.1k tokens
    MobileAuto-check passed

  • Omni

    fajarhide/omni

    A skill your agent uses when installing, verifying or configuring OMNI, when command output carries an [OMNI: ...] marker, or when output looks shorter than expected.

    366 GitHub stars~1.1k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Cue Omni Reader

    iflytek/skillhub

    Parse and understand an HTTP(S) URL or an authorized local document, audio, or video source through Cue Omni Reader when the Agent has the official Omni MCP tools.

    5.2k GitHub stars~1.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Vllm Omni Test

    vllm-project/vllm-omni

    Generate and run tests for vllm-project/vllm-omni with CI-aligned levels and markers; wire new tests into Buildkite (test-ready.yml for L1/L2, test-merge.yml for L3, test-nightly.yml for L4).

    7.1k GitHub stars~17k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • GCP Application Design Center Deploy

    google/skills

    Official

    Designs GCP infrastructure as local Terraform, validates and scans it against best practices, then imports it to Application Design Center for deployment and troubleshooting.

    21k GitHub stars~4.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from forcedotcom/sf-skills

All 252 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated yesterday
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated yesterday
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Questions about Service Omni Command Center Analyze

What does Service Omni Command Center Analyze do?

A skill your agent uses to analyze whether an org should use Command Center for Service V2 or classic Omni Supervisor and recommend the next action without making changes. Service Omni Command Center Analyze is an agent skill from forcedotcom/sf-skills. 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.

When should I use Service Omni Command Center Analyze?

Service Omni Command Center Analyze fits situations like: analyze whether an org should use Command Center for Service V2; classic Omni Supervisor and recommend the next action without making changes; assign permissions; deploy configuration.

How do I install Service Omni Command Center Analyze in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a claude-code`. Or copy the skill folder (skills/service-omni-command-center-analyze in forcedotcom/sf-skills) into .claude/skills/service-omni-command-center-analyze in your project. Claude Code loads it when a task matches its description.

How do I install Service Omni Command Center Analyze in Codex?

Run `npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a codex`. Or copy the skill folder (skills/service-omni-command-center-analyze in forcedotcom/sf-skills) into .agents/skills/service-omni-command-center-analyze in your project. Codex loads it when a task matches its description.

Can I use Service Omni Command Center Analyze in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill service-omni-command-center-analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/service-omni-command-center-analyze, .gemini/skills/service-omni-command-center-analyze, .github/skills/service-omni-command-center-analyze and .opencode/skills/service-omni-command-center-analyze in your project.

What does Service Omni Command Center Analyze need to run?

Going by SKILL.md and its folder, Service Omni Command Center Analyze needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: Python 3; A Bash shell. Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob.

Does Service Omni Command Center Analyze access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Service Omni Command Center Analyze safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Service Omni Command Center Analyze use?

Service Omni Command Center Analyze is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Service Omni Command Center Analyze use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 818 tokens, read only when the agent opens those files.

What are the alternatives to Service Omni Command Center Analyze?

Skills that share tags, products or a category with Service Omni Command Center Analyze: Gemini Omni (calesthio/OpenMontage, 66k stars), Command Center UI (sickn33/agentic-awesome-skills, 47k stars), Omni (fajarhide/omni, 366 stars) and Cue Omni Reader (iflytek/skillhub, 5.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Service Omni Command Center Analyze?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,067 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.