Agent skill · software engineering · jeremylongshore
salesloft-rate-limits
Analyze and govern Salesloft's team-wide cost budget with exact response headers, deep-page costs, fair scheduling, and bounded retries. Use when preventing or diagnosing 429 responses. Trigger with "Salesloft rate limits", "Salesloft 429", or "Salesloft request budget".
Why this skill is useful
Adds executable scripts for handling SalesLoft's cost-based rate limiting and pagination, which are not commonly found in public documentation.
What it needs
Requires axios, p-queue installed locally. Requires salesloft account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesloft Team Rate Budget Overview This skill turns Salesloft rate limiting into measured team capacity. It accounts for other integrations and deep-page multipliers rather than treating request count as cost. Prerequisites A named Salesloft team and integration owner Method/path/page inventory and recent response headers A shared per-team scheduler or limiter Replay-safe handling for any retried operation Tool Discipline Use Read, Glob, and Grep to locate pagers, retry loops, concurrency, and metrics. Use WebFetch only to confirm current official limits and endpoint costs. Use Write or Edit after the budget policy is approved. Current Contract Salesloft currently documents a default team-wide limit of 600 cost per minute; Salesloft can adjust it by customer or team. Endpoint cost defaults to 1 but can change without endpoint deprecation. Page 101-150 costs 3, 151-250 costs 8, 251-500 costs 10, and 501+ costs 30. Observe x-ratelimit-endpoint-cost and x-ratelimit-remaining-minute instead of invented per-minute header names. Another integration on the same team can consume the shared budget. Authentication Use the existing team-bound Bearer credential. Do not evade a team limit by rotating credentials or applications. Instructions 1. Instrument endpoint cost, remaining-minute value, page number, latency, status, and team alias. 2. Build a limiter keyed by team, not only process or credential. 3. Reserve headroom for interactive and recovery traffic. 4. Replace deep scans with endpoint-supported updatedat polling and durable cursors. 5. On 429, honor explicit server guidance when present; otherwise use bounded exponential backoff with jitter. 6. Retry reads and application-idempotent operations only; surface exhausted attempts. 7. Alert on sustained high endpoint cost or unexpected shared-budget depletion. Approval Boundaries Do not increase concurrency, request a provider limit adjustment, or replay uncertain writes without measured evidence and owner approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-rate-limits