Agent skill · software engineering · jeremylongshore
instantly-rate-limits
Implement Instantly API v2 workspace-wide throttling, endpoint overrides, and safe 429 recovery. Use when coordinating request budgets across workers, keys, or API versions. Trigger with "handle Instantly 429s", "set an Instantly request budget", or "throttle Instantly API workers".
Why this skill is useful
Adds executable scripts for handling Instantly API rate limits, including retry logic and concurrency control that aren't in public docs.
What it needs
Requires npm installed locally. Requires instantly account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Instantly Workspace Rate Control Overview Coordinate traffic across clients and keys so retries do not amplify throttling or duplicate writes. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result. Prerequisites The target repository, Instantly workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved API v2 key only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output. Current Contract General limits are 100 requests per second and 6,000 per minute across API v1/v2 for the whole workspace. GET /emails is limited to 20 requests per minute; other endpoints may publish independent limits. 429 is the authoritative throttling signal; retry timing must follow documented or observed response metadata. Authentication Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions. Instructions 1. Inventory every producer sharing the workspace and every endpoint-specific override. 2. Allocate a workspace request budget below both general windows. 3. Centralize token-bucket state and expose queue depth, wait time, and 429 telemetry. 4. Retry only operations proven safe, with bounded exponential backoff and jitter. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-rate-limits