Agent skill · marketing growth · jeremylongshore
instantly-performance-tuning
Analyze and tune Instantly API v2 concurrency, pagination, batching, and retries against documented workspace limits. Use when a safe integration is too slow, bursty, or wasteful. Trigger with "speed up Instantly API sync", "tune Instantly pagination", or "reduce Instantly request bursts".
Why this skill is useful
Adds executable scripts for caching and batching lead operations that optimize API performance and are not publicly documented.
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 Throughput Engineering Overview Increase throughput without violating workspace or endpoint-specific limits or duplicating mutations. 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 The general ceiling is 100 requests per second and 6,000 per minute per workspace across v1/v2 and keys. Endpoint-specific limits override the general ceiling. Bulk lead addition accepts up to 1,000 leads per request; asynchronous jobs require polling. 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. Measure route mix, payload sizes, current latency, 429s, and shared workspace traffic. 2. Classify reads, idempotent writes, non-idempotent writes, bulk operations, and background jobs. 3. Implement a workspace-wide token bucket below both general ceilings. 4. Honor endpoint overrides, jitter retryable reads, and never blindly retry non-idempotent mutations. 5. Use cursor pagination and documented bulk endpoints with bounded page/job polling. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-performance-tuning