instantly-performance-tuning
Techniques for optimizing Instantly.ai API throughput using caching, batching, and concurrent request management.
Install
mkdir -p .claude/skills/instantly-performance-tuning && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9209" && unzip -o skill.zip -d .claude/skills/instantly-performance-tuning && rm skill.zipInstalls to .claude/skills/instantly-performance-tuning
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Optimize Instantly.ai API performance with caching, batching, and connectionKey capabilities
- →Cache campaign analytics data
- →Batch lead operations with concurrency control
- →Implement cursor-based pagination
- →Manage connection reuse with Keep-Alive
- →Throttle email listing requests
How it works
This skill provides TypeScript patterns to minimize API load through caching and manages throughput using controlled concurrency and request throttling.
Inputs & outputs
When to use instantly-performance-tuning
- →Caching campaign analytics to reduce API load
- →Batching lead operations to increase throughput
- →Managing concurrent requests to avoid rate limits
- →Optimizing pagination for large datasets
About this skill
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
- Measure route mix, payload sizes, current latency, 429s, and shared workspace traffic.
- Classify reads, idempotent writes, non-idempotent writes, bulk operations, and background jobs.
- Implement a workspace-wide token bucket below both general ceilings.
- Honor endpoint overrides, jitter retryable reads, and never blindly retry non-idempotent mutations.
- Use cursor pagination and documented bulk endpoints with bounded page/job polling.
- Load-test synthetic staging data and publish before/after evidence plus rollback thresholds.
Approval Boundaries
Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Output
Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
Error Handling
| Condition | Response |
|---|---|
401 | Stop and verify that the bearer key exists, is current, and was not revoked. |
403 | Stop and compare the operation with its exact required scope; do not broaden to all:all by default. |
429 | Coordinate the workspace-wide budget, honor endpoint overrides, and bound retries. |
| Schema or tenant mismatch | Fail closed, preserve redacted evidence, and do not retry a mutation. |
Examples
Use a compact handoff that makes scope, mutation authority, and evidence reviewable.
Input:
workload=lead-import; rows=10000; workspace-rps-budget=80
Expected handoff:
batch=1000; concurrency=measured; duplicate-writes=0
Resources
When not to use it
- →When cache TTL is too long for real-time data needs
- →When API rate limits are not a concern
Prerequisites
Limitations
- →Email listing endpoint has a strict 20 req/min limit
- →Stale cache data if TTL is not managed
How it compares
It replaces sequential, unmanaged API calls with optimized patterns like pre-fetching and rate-limit-aware batching.
Compared to similar skills
instantly-performance-tuning side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| instantly-performance-tuning (this skill) | 0 | 2mo | Caution | Intermediate |
| documenso-performance-tuning | 0 | 2mo | Review | Intermediate |
| gamma-performance-tuning | 0 | 2mo | No flags | Intermediate |
| juicebox-prod-checklist | 1 | 2mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
documenso-performance-tuning
jeremylongshore
Optimize Documenso integration performance with caching, batching, and efficient patterns. Use when improving response times, reducing API calls, or optimizing bulk document operations. Trigger with phrases like "documenso performance", "optimize documenso", "documenso caching", "documenso batch operations".
gamma-performance-tuning
jeremylongshore
Optimize Gamma API performance and reduce latency. Use when experiencing slow response times, optimizing throughput, or improving user experience with Gamma integrations. Trigger with phrases like "gamma performance", "gamma slow", "gamma latency", "gamma optimization", "gamma speed".
juicebox-prod-checklist
jeremylongshore
Execute Juicebox production deployment checklist. Use when preparing for production launch, validating deployment readiness, or performing pre-launch reviews. Trigger with phrases like "juicebox production", "deploy juicebox prod", "juicebox launch checklist", "juicebox go-live".
perplexity-architecture-variants
jeremylongshore
Choose and implement Perplexity validated architecture blueprints for different scales. Use when designing new Perplexity integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Perplexity applications. Trigger with phrases like "perplexity architecture", "perplexity blueprint", "how to structure perplexity", "perplexity project layout", "perplexity microservice".
idmp
ha0z1
Use when you need to deduplicate concurrent or repeated async calls, prevent duplicate API requests, cache async function results, add automatic retry with exponential backoff, memoize heavy computation wrapped in Promise, replace SWR/Provider for request sharing, invalidate cache with flush, or per
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).