Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
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…
$ npx skills add forcedotcom/sf-skills --skill service-omni-channel-limits-analyze -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-analyze --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "service-omni-channel-limits-analyze" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyze into .claude/skills/service-omni-channel-limits-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-omni-channel-limits-analyze", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyzeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add forcedotcom/sf-skills --skill service-omni-channel-limits-analyze -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-analyze --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/service-omni-channel-limits-analyze .agents/skills/service-omni-channel-limits-analyze && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "service-omni-channel-limits-analyze" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyze into .agents/skills/service-omni-channel-limits-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-omni-channel-limits-analyze", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill service-omni-channel-limits-analyze -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-analyze --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/service-omni-channel-limits-analyze .cursor/skills/service-omni-channel-limits-analyze && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "service-omni-channel-limits-analyze" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyze into .cursor/skills/service-omni-channel-limits-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-omni-channel-limits-analyze", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/service-omni-channel-limits-analyze--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill service-omni-channel-limits-analyze -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-analyze --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/service-omni-channel-limits-analyze .gemini/skills/service-omni-channel-limits-analyze && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "service-omni-channel-limits-analyze" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyze into .gemini/skills/service-omni-channel-limits-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-omni-channel-limits-analyze", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-analyzeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add forcedotcom/sf-skills --skill service-omni-channel-limits-analyze -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/service-omni-channel-limits-analyze .github/skills/service-omni-channel-limits-analyze && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "service-omni-channel-limits-analyze" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyze into .github/skills/service-omni-channel-limits-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-omni-channel-limits-analyze", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill service-omni-channel-limits-analyze -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills service-omni-channel-limits-analyze --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/service-omni-channel-limits-analyze .opencode/skills/service-omni-channel-limits-analyze && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "service-omni-channel-limits-analyze" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-omni-channel-limits-analyze into .opencode/skills/service-omni-channel-limits-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-omni-channel-limits-analyze", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
service-omni-channel-limits-analyzeA 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. 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.
Read from SKILL.md and the folder at commit 4bbae5c. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteGrepGlobFrom allowed-tools in the SKILL.md frontmatter.
Ships 3 files in scripts/ (Python and Shell), which the agent can run.
Shell commands in SKILL.md call:
sfbashpython3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Bash, Read, Write, Grep, GlobAutomated 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.
The full file from forcedotcom/sf-skills at commit 4bbae5c, republished under its Apache-2.0 licence (© forcedotcom). 340 words, ~964 tokens.
.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.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.
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.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.
The script emits one JSON object:
skill: service-omni-channel-limits-analyzestatus: analyzed or blockedrouting_model: enhanced or legacymetrics.current_pending_service_routings: live count, comparison maximum, approximate percentage, and source labelsmetrics.pending_service_routing_rate_per_hour: unavailable live value, reference maximum, and source labelscaveats: mandatory accuracy boundariesblocking_issue: actionable failure reason or nullIf PendingServiceRouting cannot be queried, return status: blocked. Do not reinterpret an unavailable object, missing feature, or permission failure as zero usage.
service-omni-channel-inventory-analyze.service-omni-channel-setup-coordinate; this limits analyzer remains read-only.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
SKILL.md and 4 other files (scripts, references) in skills/service-omni-channel-limits-analyze of forcedotcom/sf-skills.
Open the folder on GitHubat commit 4bbae5c
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Service Omni Channel Limits Analyze this skillforcedotcom/sf-skills | 1.1k | — | ~964 | Automated safety check: Notes | Apache-2.0 | |
| Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib | 154 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Sf DatacloudJaganpro/sf-skills | 424 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Soql Lib Selectorbeyond-the-cloud-dev/soql-lib | 154 | — | ~2k | Automated safety check: Pass | MIT | |
| Dev SetupPortwood-Global-Solutions/Portwood | 126 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Sf FlowJaganpro/sf-skills | 424 | — | ~1.8k | Automated safety check: Pass | MIT |
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
Jaganpro/sf-skills
Creates and validates Salesforce Flows with 110-point scoring.
gmapsscraper/google-maps-agent-skills
Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Works with
Categories
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.