Agent skill · software engineering · jeremylongshore
algolia-rate-limits
Monitor and optimize Algolia request pressure using observed responses and bounded client behavior. Use when requests return 429, queues grow, or search and indexing compete for capacity. Trigger with "Algolia rate limit", "Algolia 429", or "throttle indexing".
Why this skill is useful
Provides specific implementation patterns for handling Algolia's rate limits and backoff strategies that the AI wouldn't reliably generate on its own.
What it needs
Requires p-queue installed locally. Requires algolia account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Algolia Rate-Pressure Handling Overview This skill avoids invented universal quotas. It distinguishes key restrictions, current contractual usage, indexing pressure, transient transport failures, and application amplification using actual response evidence. Prerequisites A named repository, environment, and Algolia application or index in scope The local lockfile and installed client types as implementation authority A safe read-only query or explicitly disposable test target Current first-party documentation for any provider behavior that affects the change Tool Discipline Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan. Current Contract Interpret a 429 from its status, message, operation, request ID, and current account terms. Inspect installed client behavior before layering application retries on top of SDK host retry. Bound attempts, elapsed time, concurrency, and queue depth; retry only operations whose semantics are safe. Protect interactive search from batch indexing through workload scheduling and backpressure. Authentication Use operation-specific, least-privilege keys. Never raise limits by replacing a restricted key with an Admin key or by removing tenant safeguards. Instructions 1. Capture the failing operation, response, request ID, client version, concurrency, queue depth, and traffic source. 2. Check key restrictions and current usage or contract evidence without assuming a fixed quota. 3. Identify amplification from duplicate clients, unbounded concurrency, retries, bots, or oversized batches. 4. Define a retry budget with eligible errors, maximum attempts, elapsed timeout, jitter, and cancellation. 5. Apply concurrency limits or scheduling at the producer and test partial failure and shutdown. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-rate-limits