Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/algolia-rate-limits

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-rate-limits

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈71 tokens for metadata: the name and description. ≈852 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈283 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Verify search health, queue recovery, idempotency, and alerting under controlled pressure.

Approval Boundaries

Do not load-test production, remove rate restrictions, increase plan limits, or retry non-idempotent work without owner approval.

Output

Return the observed limit evidence, pressure source, retry and queue policy, test results, residual capacity risk, and any commercial decision requiring an account owner.

Error Handling

Condition Response
429 message ambiguous Retain request ID and consult current provider support or docs.
Retry storm begins Open the circuit and drain or shed work.
Queue exceeds bound Stop producers and preserve work for controlled replay.
Plan change proposed Separate the commercial approval from the technical fix.

Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

operation=saveObjects; status=429; concurrency=40; sdk=5.59.0

Expected handoff:

cause=producer-amplification; concurrency=4; retry-budget=bounded; recovery=verified

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides guidance for monitoring and optimizing Algolia API request pressure. It includes standard security practices such as least-privilege authentication. The analysis identifies a minor surface for indirect prompt injection because the skill captures and processes external API response messages without explicit sanitization instructions.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [operation]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "reliability"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-rate-limits