Agent skill

Service Omni Channel Limits Analyze

by forcedotcom in forcedotcom/sf-skills

A skill your agent uses to report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a…

Apache-2.0Auto-check: notesSales & Support

Install Service Omni Channel Limits Analyze

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

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

GitHub CLI
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-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-channel-limits-analyze .claude/skills/service-omni-channel-limits-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-channel-limits-analyze
GitHub stars
1.1k
Token cost
~964 tokens
SKILL.md length
340 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 report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a…

  • Report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count
  • SKILL.md covers Inputs, Run, Output contract and Boundaries, plus 1 more section
  • Runs Python and Shell scripts from its folder; calls sf, bash and python3
  • Compare it with an admin-supplied maximum

What it does

Service Omni Channel Limits Analyze is an agent skill from forcedotcom/sf-skills. Use to report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a labeled routing-model reference default, and explain which live values are unavailable through supported APIs. TRIGGER when: check Omni-Channel limits, inspect PSR limits, analyze PendingServiceRouting usage, review pending routing capacity, or report queued work usage. Do not use to change limits or scrape Salesforce Setup.

Its SKILL.md is about 960 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`).

It sits in Sales & Support, covering CRM management and Web scraping. It works with Salesforce. 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

  • Report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count
  • Compare it with an admin-supplied maximum
  • A labeled routing-model reference default
  • Explain which live values are unavailable through supported APIs

Example prompts

  • “/service-omni-channel-limits-analyze”

Requirements

  • Python 3
  • A Bash shell
  • Pre-approved tools (allowed-tools): Bash, Read, Write, 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
    • Write
    • 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:

    • sf
    • bash
    • python3

    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 Channel Limits Analyze loads about 964 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 135 tokens; SKILL.md has 340 words of instructions outside code blocks.

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

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, Write, 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). 340 words, ~964 tokens.

Download SKILL.mdSave it as .claude/skills/service-omni-channel-limits-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-channel-limits-analyze
description
Use to report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a labeled routing-model reference default, and explain which live values are unavailable through supported APIs. TRIGGER when: check Omni-Channel limits, inspect PSR limits, analyze PendingServiceRouting usage, review pending routing capacity, or report queued work usage. Do not use to change limits or scrape Salesforce Setup.
allowed-tools
Bash, Read, Write, Grep, Glob
metadata.version
1.0
metadata.domains
Service
metadata.minApiVersion
66.0
metadata.relatedSkills
service-omni-channel-inventory-analyze, service-omni-channel-setup-coordinate

service-omni-channel-limits-analyze

Report the Pending Service Routing usage that can be obtained safely through supported customer-org APIs. The Salesforce Setup → Omni-Channel → Limits page is read-only and also displays internal values that are not exposed through REST, Tooling, Metadata, or Connect APIs. This skill reports the live PSR count and labels every non-verifiable value explicitly.

Inputs

bash
bash scripts/analyze.sh <org-alias> [--routing-model enhanced|legacy] [--max-psrs <integer>]
  • org-alias is required and must already be authenticated with Salesforce CLI.
  • --routing-model defaults to enhanced. It selects only the reference maximum used when --max-psrs is absent.
  • --max-psrs accepts an administrator-provided maximum from 1 through 1,000,000. It is still labeled as not API-verified.

Run

Invoke scripts/analyze.sh with the target org and rely on its JSON result for the live count, labeled comparison values, unavailable hourly values, and blocking details. The script invokes sf org display and sf data query internally; do not reproduce their query or calculation logic outside the script.

To verify the bundled script contract after a change, run python3 scripts/tests/test_limits_analyze_contracts.py; the test module loads its local scripts/tests/_bootstrap.py fixture automatically.

Output contract

The script emits one JSON object:

  • skill: service-omni-channel-limits-analyze
  • status: analyzed or blocked
  • routing_model: enhanced or legacy
  • metrics.current_pending_service_routings: live count, comparison maximum, approximate percentage, and source labels
  • metrics.pending_service_routing_rate_per_hour: unavailable live value, reference maximum, and source labels
  • caveats: mandatory accuracy boundaries
  • blocking_issue: actionable failure reason or null

If PendingServiceRouting cannot be queried, return status: blocked. Do not reinterpret an unavailable object, missing feature, or permission failure as zero usage.

Boundaries

  • Never scrape, replay, or submit the Visualforce Setup page. Its session state and controller are not a supported customer API.
  • Never describe a reference default as the org's configured maximum.
  • Never fabricate the live hourly rate or compute its utilization percentage.
  • Never mutate routing, queues, agents, limits, or metadata.
  • Treat the PSR count as a point-in-time snapshot that can change while work is routed.
  • For a complete channel and routing inventory, use service-omni-channel-inventory-analyze.
  • For a user-approved end-to-end Omni setup, hand off to service-omni-channel-setup-coordinate; this limits analyzer remains read-only.

Reference

Read references/api-notes.md when explaining why the report cannot exactly reproduce every value on the Setup page.

© 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-channel-limits-analyze of forcedotcom/sf-skills.

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

Open the folder on GitHubat commit 4bbae5c

Compare with similar skills

Service Omni Channel Limits 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 Channel Limits Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Service Omni Channel Limits Analyze this skillforcedotcom/sf-skills1.1k—~964Automated safety check: NotesApache-2.0
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib154—~4.3kAutomated safety check: PassMIT
Sf DatacloudJaganpro/sf-skills424—~2.7kAutomated safety check: PassMIT
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib154—~2kAutomated safety check: PassMIT
Dev SetupPortwood-Global-Solutions/Portwood126—~1.1kAutomated safety check: PassApache-2.0
Sf FlowJaganpro/sf-skills424—~1.8kAutomated safety check: PassMIT

Similar skills

  • Soql Lib Query Builder

    beyond-the-cloud-dev/soql-lib

    Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).

    154 GitHub stars~4.3k tokensUpdated 8 days ago
    Sales & SupportAuto-check passed
  • Sf Datacloud

    Jaganpro/sf-skills

    Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.

    424 GitHub stars~2.7k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed
  • Soql Lib Selector

    beyond-the-cloud-dev/soql-lib

    Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.

    154 GitHub stars~2k tokensUpdated 8 days ago
    Sales & SupportAuto-check passed
  • Dev Setup

    Portwood-Global-Solutions/Portwood

    Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.

    126 GitHub stars~1.1k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Sf Flow

    Jaganpro/sf-skills

    Creates and validates Salesforce Flows with 110-point scoring.

    424 GitHub stars~1.8k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed
  • Google Maps Export

    gmapsscraper/google-maps-agent-skills

    Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).

    132 GitHub stars~1.2k tokensUpdated 4 mo ago
    Sales & SupportAuto-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
  • Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated yesterday
    Auto-check: notes
  • 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

Works with

Categories

Questions about Service Omni Channel Limits Analyze

What does Service Omni Channel Limits Analyze do?

A skill your agent uses to report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a…. Service Omni Channel Limits Analyze is an agent skill from forcedotcom/sf-skills. Use to report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a labeled routing-model reference default, and explain which live values are unavailable through supported APIs.

When should I use Service Omni Channel Limits Analyze?

Service Omni Channel Limits Analyze fits situations like: report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count; compare it with an admin-supplied maximum; A labeled routing-model reference default; explain which live values are unavailable through supported APIs.

How do I install Service Omni Channel Limits Analyze in Claude Code?

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

How do I install Service Omni Channel Limits Analyze in Codex?

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

Can I use Service Omni Channel Limits 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-channel-limits-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-channel-limits-analyze, .gemini/skills/service-omni-channel-limits-analyze, .github/skills/service-omni-channel-limits-analyze and .opencode/skills/service-omni-channel-limits-analyze in your project.

What does Service Omni Channel Limits Analyze need to run?

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

Does Service Omni Channel Limits 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 Channel Limits 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 Channel Limits Analyze use?

Service Omni Channel Limits 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 Channel Limits Analyze use?

About 964 tokens (SKILL.md is roughly 3.9k 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 328 tokens, read only when the agent opens those files.

What are the alternatives to Service Omni Channel Limits Analyze?

Skills that share tags, products or a category with Service Omni Channel Limits Analyze: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars) and Dev Setup (Portwood-Global-Solutions/Portwood, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Service Omni Channel Limits 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.