fsl-capacity-planning SKILL.md skillA
fsl-capacity-planning from pranavnagrecha/awesomesalesforceskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranavnagrecha/awesomesalesforceskills/fsl-capacity-planning@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranavnagrecha/awesomesalesforceskills
- Path
skills/admin/fsl-capacity-planning/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Aug 14, 2026
- First version recorded
- Apr 10, 2026
- Size
- 22,431 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use this skill to configure and manage Field Service Lightning workforce capacity — covering ServiceResourceCapacity for individual resource caps, WorkCapacityLimit for territory-level demand throttling, and reporting strategies for capacity vs. utilization analysis. NOT for resource skills, certifications, or preference setup — use admin/fsl-resource-management. NOT for work rules and service objectives — use admin/fsl-scheduling-policies. NOT for Omni-Channel agent capacity — use…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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`, and `ServiceResource` objects. - 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. …
Read the whole file at its exact version.
How to install
mdr add pranavnagrecha/awesomesalesforceskills/fsl-capacity-planning@sha256:8fc0c049b9c22d8aThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_k4dzfuhrjzjs3qmm)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 10, 2026 and Aug 14, 2026, about one every 126 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-14 | 25df1fd | 22,431 B | A | view · diff |
| v1.0.0 | 2026-04-10 | 7b51c41 | 22,330 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (22431 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pranavnagrecha/awesomesalesforceskills · 19 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k4dzfuhrjzjs3qmm GET https://markdownregistry.com/api/v1/resolve?ref=pranavnagrecha/awesomesalesforceskills/fsl-capacity-planning GET https://markdownregistry.com/api/v1/blob/8fc0c049b9c22d8a1259e27bdda8e5307ce05d556823a3b7aca1c28b9e54138b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.