Agent skill · software engineering · jeremylongshore
salesforce-rate-limits
Analyze and govern Salesforce API, asynchronous, bulk, and event capacity from current org allocations and usage evidence. Use when preventing or resolving exhaustion. Trigger with "govern Salesforce limits".
Why this skill is useful
Adds executable scripts for managing Salesforce API limits, including retry logic and quota monitoring that are not commonly found in public documentation.
What it needs
Requires jsforce installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Org Limit and Capacity Governance Overview Treat limits as shared, time-varying org contracts and allocate headroom across integrations without publishing fixed universal thresholds. Prerequisites Authorized org, workload, API and event modes, business priority, and peer integrations Current Limits resource, Sforce-Limit-Info, job, event-usage, and application telemetry Platform, integration, incident, and business owners with a deferral policy Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract The versioned Limits REST resource returns maximum and remaining allocations and can lag consumption by up to five minutes. Sforce-Limit-Info reports REST API usage; names, allocations, windows, grace behavior, and entitlements vary by org, edition, license, API version, and workload. Authentication Use an approved read-only principal with the permission required to view limits. Do not expose tokens, org identifiers, or unrelated allocation details in public metrics or receipts. Instructions 1. Inventory every workload sharing the org, its API mode, priority, schedule, concurrency, retry behavior, and owner. 2. Discover a supported API version and capture current Limits and response-header evidence with timestamps. 3. Map relevant REST, bulk, async, Apex, storage, and event allocations to workloads and business deadlines. 4. Model normal, burst, retry-storm, backfill, and incident demand with an explicit measurement-lag safety margin. 5. Define admission, concurrency, batching, backpressure, deferral, and stop policies per priority class. 6. Test the policy with synthetic work in an authorized non-production org and prove hard exhaustion is not blindly retried. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-rate-limits--af0888