Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill fsl-capacity-planninggit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/fsl-capacity-planning)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/fsl-capacity-planning"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/fsl-capacity-planning/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/fsl-capacity-planning"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/fsl-capacity-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.04492 |
| Opus 5 | $0.00041 | $0.02246 |
| Sonnet 5 | $0.00016 | $0.00898 |
| Haiku 4.5 | $0.00008 | $0.00449 |
Grade A, and why
fsl-capacity-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FSL Capacity Planning
This skill activates when a practitioner needs to configure, audit, or report on Field Service Lightning workforce capacity — including per-resource capacity caps via ServiceResourceCapacity, territory-level demand throttling via WorkCapacityLimit, and strategies for measuring capacity utilization. It addresses both mechanisms the FSL scheduling engine uses to constrain appointment volume and explains how the two mechanisms interact.
Before Starting
Gather this context before working on anything in this domain:
- Confirm that Field Service is enabled (Setup > Field Service Settings) and that the running user has access to
ServiceResourceCapacity,WorkCapacityLimit, andServiceResourceobjects. - Determine which capacity mechanism applies: resource-level capacity (
ServiceResourceCapacity) controls how many hours or appointments a single resource can take in a period; territory-level capacity (WorkCapacityLimit) controls how many appointments of a given work type a territory accepts in a time window. These are independent and additive — an appointment must satisfy both constraints before it can be scheduled. - Identify whether resources are marked
IsCapacityBased = true.ServiceResourceCapacityrecords only take effect on resources whereIsCapacityBased = trueon theServiceResourcerecord. Standard time-slot-based technicians ignore these records entirely. - Establish the scheduling horizon.
ServiceResourceCapacityandWorkCapacityLimitrecords cover explicit date ranges. Gaps in coverage silently prevent scheduling without any error shown to dispatchers or optimization logs. - Note that there are no seasonal capacity templates in FSL. Bulk updates to
WorkCapacityLimitrecords (e.g., holiday reductions, peak-season increases) must be performed via Data Loader or Apex — there is no native UI for mass date-range updates.
Core Concepts
Two Capacity Mechanisms: Resource-Level vs. Territory-Level
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 254 lines · 82 tokens per session scan A a278b315d4e2
fsl-capacity-planning is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 4,492 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
setup-platform-development
Help set up the platform development policy — contribution mode, governance, and sharing.
platform-management
Workspace OS charter for Auto — runtime governor of the agent organisation, routing, cadence, authority, governance, and full platform operations reference.
scheduler
Natural language task scheduling for Kite. Create, list, and cancel scheduled jobs in plain English with a human-readable registry of what's running and why.
analytics-adoption-strategy
Use this skill when driving adoption of CRM Analytics (Einstein Analytics) across an org — the Analytics Adoption App for measuring who uses which dashboards, embedding analytics into Lightning pages, pinning dashboards to the Analytics home page, self-service personas, and analytics success metrics. Triggers…
cpq-approval-workflows
Configuring or troubleshooting Salesforce CPQ Advanced Approvals: SBAAApprovalRulec, SBAAApprovalVariablec for cross-line aggregation, SBAAApprovalChainc for ordered approver sequences, escalation timeouts, Smart Approvals for re-quote skip logic, and the managed package's permission sets. Trigger keywords: CPQ…
ai-adoption-change-management
Use this skill when planning or executing the human side of an Agentforce or Einstein AI feature rollout — user trust-building, AI-specific training, structured feedback collection via the Feedback API, and adoption measurement via Agentforce Analytics. NOT for turning the Einstein for Sales features on — use…