Agent skill · data analytics · jeremylongshore
algolia-common-errors
Diagnose Algolia request, credential, index, task, and query failures from concrete evidence. Use when an integration returns 4xx or 5xx responses, stale results, or unexpected empty hits. Trigger with "debug Algolia error", "Algolia 403", or "Algolia search failed".
Why this skill is useful
Provides specific troubleshooting commands and patterns for handling Algolia API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires jq 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 Error Triage Overview This skill turns an Algolia symptom into a reproducible diagnosis. It favors the response status, message, request ID, client version, operation, and target index over generic error folklore. 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 A 403 is an authorization fact, not proof that an unrestricted key is required. A successful write is asynchronous; compare the returned task ID and wait behavior before calling data stale. A 404 can identify a missing index, application, route, or regional endpoint; preserve the full response. A 429 must be interpreted from the returned message and current plan or key restrictions, not from a guessed universal quota. Authentication Inspect only redacted key metadata and ACL intent. Never print, paste, or replace a credential with an Admin key merely to make a failing request succeed. Instructions 1. Capture the smallest failing call, status, message, request ID, application ID suffix, index name, and package version. 2. Classify the operation as search, indexing, settings, key management, analytics, or events. 3. Compare the operation with the intended key ACLs and index restrictions. 4. Reproduce against a safe test index or read-only query with the same client boundary. 5. Check task completion, index spelling, filters, attributes, and environment routing in that order. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-common-errors